Shocker CosmosDB

Originally Azure created DocumentDB that it later changed the name to CosmosDB. Now Amazon has taken the DocumentDB name. But that is not all that is similar. CosmosDB is also compatible with Mongo APIs:…

The Azure Cosmos DB’s API for MongoDB is compatible with MongoDB Server version 3.2 by default. The supported operators and any limitations or exceptions are listed below. Features or query operators added in MongoDB version 3.4 are currently available as a preview feature. Any client driver that understands these protocols should be able to connect to Azure Cosmos DB’s API for MongoDB.

The MongoDB aggregation pipeline is also currently available as a separate preview feature.

Only up to version 3.4, not 3.6, but has not hurt MongoDB. And migration and functionality are not the same.

Here a business user switched to CosmosDB but found some material short comings:…

Nevertheless, in the end, he says they are satisfied (be tough to say otherwise after all the work out in to make it so).

On the other hand Mongo likes to talk about customers who tried Cosmos and switched to Mongo.

When Microsoft announced their product no one said a word. Now that Amazon has there is panic. So what Amazon did is what Microsoft did earlier in 2018, except w 3.6 version instead of 3.4.

This is not a winner take all market but a winner take most. Does AWS following Microsoft change the winner take most? Or is Mongo no longer the winner w emulators on the tail?




It is hard to predict where the NoSQL sector will go in the long run. One possibility is that a standard query language, much like ANSI SQL in the 1980’s, will be developed and shared across all major NoSQL databases. Another is that ANSI SQL itself will continue to evolve until it is capable of serving that role.

Or perhaps the existing APIs such as found in MongoDB will become de facto standard, informally agreed upon by major vendors but never formally approved by a standards body.

In the meantime, it is unlikely that any one NoSQL database will stay in a dominant position so long as the competitors can easily copy their REST APIs. Even if CosmoDB manages to unseat MongoDB or Cassandra, another database/cloud vendor such as Amazon or Google can do the same to them.

This article lays out the dilemma quite well. Even if MongoDB becomes the industry standard (as usual, only Mongo is mentioned as such) can Mongo maintain increasing returns if its APIs can simply be used?



Still numbers talk and Mongo remains far and away the leader. At least one measure anyways. Amazon and Microsoft remain well below despite their inherent marketing advantages.



Very interesting. The SQL world is a standardized language that is then extended by all the major players. The Oracle SQL is a bit different in extensions than IBM, for example. And nobody writes major critical apps w/o taking advantage of the extensions. So… have fun porting from Oracle to IBM, even though both are SQL. We might see the beginnings of this in the NoSQL world right now folks.

1 Like