What do you suggest one does if one has to run on Azure though?
PS Azure Cosmos is not a real product, it is a beta toy that Microsoft just has made expensive enough that people think it cannot possibly be as bad as it is..
what kind of problems you ran into with Cosmos?
Last I checked, that “compatibility” run at least a couple major version behind the real MongoDB.
To be fair, the same is probably also true with AWS’s DocumentDB
Most obvious indicator is DocumentDB is single node write whereas Mongo is really not, coming from Aurora Postgres.
1. yugabytedb (postgres compatible)
2. cockroachdb (postgres compatible)
3. tidb (mysql compatible)
You could self-host these on azure or subscribe to each of their managed service offering.
Of course, sticker price for managed will be more expensive than self-hosted enterprise product which itself will be more expensive than the self-hosted, community-supported, open-source option (which seems to be a real option with YugabyteDB).
They've just selected a few features from postgres which they're compatible in.
The PostgreSQL organisation should create some trademarked badges to properly label the levels of compatibility other products offer.
Would be interested to hear your challenges.