Now that Geoff has indicated that they are switching over to more professional web developers the need for the compression algorithm that was introduced in MongoDB 3.0 is more needed than ever.
We can’t seriously spend x-times more money on our scalable solution just because MDG is trailing the latest MongoDB version by years (MongoDB version 2.6 was released in April 2014, see here: https://en.wikipedia.org/wiki/MongoDB) and our database isn’t compressed (I read examples from going down from 12GB to 2GB with MongoDB, that’s a huge amount of operating cost saved.
So now we’re having version 3.2 and all I hear from Geoff on what is coming up in the future should sound nice to the JV’s (if that plan works out and the pros can be convinced to use Meteor). But in order to achieve that the database can’t be 2 versions behind.
Would be interested to hear some official words on this from MDG.