Why DocumentDB can be a win for MongoDB

To put it more bluntly: Control is finite; influence is compounding. SQL didn’t kill Oracle or SQL Server—it made them bigger businesses. Kubernetes didn’t commoditize cloud—it redirected competition toward managed experience, security, and reliability. The same dynamic is available to MongoDB.

Of course MongoDB won’t be the only vendor that benefits, but that’s a feature, not a bug. AWS, Google, and others are piling into DocumentDB because they, too, hope to benefit (and will invest commensurate with those expected returns). My employer, Oracle, hasn’t announced support for the standard, yet Oracle would also benefit. Oracle Database 23ai introduced JSON Relational Dualitywhich lets developers present and update the same underlying relational data as updatable JSON documents—without duplicating data—and access it through MongoDB-compatible APIs, REST, and SQL. It’s very cool. Standards tend to enable this kind of “have it both ways,” and ecosystems tend to amplify it. If a neutral document standard nails API behavior and semantics, vendors can innovate on how they store and optimize data beneath that API—exactly what Oracle is doing by unifying document and relational on one engine.

Otherwise stated, when the surface area (the developer experience and API) is predictable, buyers choose based on operational excellence, scale, governance, and adjacent capabilities (analytics, AI, security). That’s where MongoDB has invested for a decade with Atlas. A standard doesn’t erase that; it spotlights it.