Now there is good news :) You can easily use the outlined MongoDB database with Meteor with a few settings.
Although the Meteor core development team has not yet added Oplog Tailing support to outline their RoadMap , the workaround is so simple. You just add these 2 Meteor: cultofcoders:redis-oplog and disable-oplog , add another Redis server, tweak your code a bit, and you're good to go.
The reason Oplog Tailing does not work with the fragmentation database MongoDB is because the core development team has not yet planned to support it. In fact, now you can add support for the plastered database. If you add a bunch of new records and read Oplogs using tail cursors from all the fragments, you will notice that the MognoDB balancer will move the data, say, from shard01 to shard02 , where record ID 0001 was removed from shard01 and added to shard02 . This situation seems to confuse the Meteor, as it does not know if the records are really deleted / added by users or the MongoDB balancer. However, there is a way to find out if users or the MongoDB balancer / added the data, because we can distinguish the fromMigrate flag - read more about this in the MongoDB Official Representative website blog - so now we can wait for the update from the main development team or work with several tricks .
And the most promising workaround I have found so far is the Meteor package called cultofcoders:redis-oplog . It opens and is available on Github (check out their repository for full documentation. It's very easy to use). The idea of this package is to use another Redis server as a pub and sub system - it does not store any data. it's just for pub and sub - instead of Meteor, which rely heavily on Oplog. Thus, we do not need to worry about Oplog for a plastered database that Meteor has not yet supported. Redis is mature and used in production by many large companies. It is fully compatible with Meteor, and you do not need to change the way you use Meteor. However, you need to tweak the code a bit when updating the collection data to post changes to Redis , and then the cultofcoders:redis-oplog will handle the rest.