6 ms·
Looking through the supported APIs (https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html https://docs.aws.amazon.com/documentdb/latest/d
by bnjmn 8y ago
Looking through the supported APIs (https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html https://docs.aws.amazon.com/documentdb/latest/developerguide...), it appears DocumentDB has no support for Mongo's oplog (https://docs.mongodb.com/manual/core/replica-set-oplog/ https://docs.mongodb.com/manual/core/replica-set-oplog/), or change streams (https://docs.mongodb.com/manual/changeStreams https://docs.mongodb.com/manual/changeStreams), which I guess is no surprise because change streams were introduced in Mongo 4, whereas DocumentDB copied the 3.6 API. So DocumentDB seems much less useful as a reactive data store than MongoDB.
In other words, DocumentDB is only a drop-in replacement for MongoDB if you weren't using any of the features Amazon decided not to support.
Happy to be corrected if I'm misreading the documentation!
- ahachete 8y agoI agree with you. Having said that, when we were working on https://www.torodb.com https://www.torodb.com we discussed how we'd implement the oplog. And actually, based on PostgreSQL's logical decoding (LD), it wouldn't have been a great deal (there are some gotchas, but LD brings much of what you need. So I won't be surprised if this would be implemented sooner than later.
- indogooner 8y agoInteresting. I think the sole purpose of this product is to wean existing Mongo customers (3.6-). And only those customers who are happy with Mongo API but not MongoDB itself. Is that such a huge market? Would be curious to see how this solution is adopted.
- InspiredIdiot 8y agoAlso the aggregation pipeline is seriously hobbled with way more No-s than Yes-es over here https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis-aggregation-pipeline.html https://docs.aws.amazon.com/documentdb/latest/developerguide...