Microsoft-Backed DocumentDB Challenges MongoDB With PostgreSQL Foundation and Open Governance

DocumentDB combines MongoDB-compatible document handling with PostgreSQL's reliability under Linux Foundation governance. Backed by Microsoft, AWS and others, it targets AI workloads with native vector search and eliminates separate vector stores. The open project now challenges proprietary options with true portability.
Microsoft-Backed DocumentDB Challenges MongoDB With PostgreSQL Foundation and Open Governance
Written by Dave Ritchie

Developers have long faced a choice. Stick with the familiar document model of MongoDB. Or accept the power and reliability of PostgreSQL. A new project removes the trade-off.

DocumentDB delivers native BSON support on top of PostgreSQL. It speaks the MongoDB wire protocol. Yet it taps the full SQL capabilities, proven durability, and vast extension ecosystem of its relational host. The project started inside Microsoft in 2024 as two PostgreSQL extensions. It now sits under the Linux Foundation with a permissive MIT license and broad industry backing.

From Microsoft Experiment to Neutral Open Standard

The origins trace to a straightforward goal. Give teams document flexibility without sacrificing the battle-tested strengths of Postgres. Kirill Gavrylyuk, vice president at Microsoft, put it plainly. “We built DocumentDB with a simple goal: give developers an open document database with the flexibility of NoSQL and the power, reliability, openness, and ecosystem of Postgres.” (Microsoft Open Source Blog, August 25, 2025)

By August 2025 the project had gathered nearly 2,000 GitHub stars and hundreds of contributions. Momentum convinced Microsoft to hand governance to the Linux Foundation. The move secured vendor-neutral stewardship. It also invited wider participation from AWS, Google Cloud, Yugabyte, Supabase, Snowflake, Rippling and others. Jim Zemlin, executive director of the Linux Foundation, saw larger implications. “DocumentDB fills a critical gap in the document database ecosystem, attracting contributors, users and champions. What’s even more exciting is it provides an open standard for document based applications, like what SQL did for relational databases.” (Linux Foundation, August 25, 2025)

Today the GitHub repository at github.com/documentdb/documentdb shows over 3,400 stars. Recent commits address aggregation improvements, RBAC support, dynamic cursors and Docker fixes. A technical steering committee draws members from Microsoft, Amazon, Yugabyte and other sponsors. The project remains PostgreSQL-first. It avoids forking the core engine. Instead it adds BSON datatype handling, a protocol gateway that translates MongoDB API calls into PostgreSQL queries, and rich indexing options.

That architecture matters. Single-field, compound, text, geospatial and nested-field indexes sit alongside pgvector-powered vector indexes. Full-text search, geospatial queries and complex aggregations run natively. Developers write familiar MongoDB-style queries yet gain PostgreSQL’s transaction guarantees and extension model. But the real draw may lie elsewhere.

Adam Abrevaya, director of Amazon DocumentDB, welcomed the collaboration. “AWS is excited to contribute to the open source DocumentDB project, now stewarded by the Linux Foundation. DocumentDB, a permissively licensed database for implementing the MongoDB API, and an extension to PostgreSQL, the world’s leading open source database, advances a future where developers can rest assured that their applications are portable and compatible.” (Linux Foundation press release)

Bruce Momjian, founding member of the PostgreSQL core team, offered historical perspective. “The idea of using Postgres in this way has been around for a long time so I am glad it is now getting serious traction. DocumentDB should be an interesting alternative to users wanting an open source implementation.” (Linux Foundation press release)

Portability sits at the center. Run DocumentDB locally with a single Docker command on port 10260. Deploy via the Kubernetes operator to kind, minikube, hybrid clouds or multi-cluster setups. High-availability replication and self-hosted operation give teams control that managed services cannot match. SCRAM authentication and MIT licensing remove lock-in worries. The operator preview, detailed in a November 2025 Microsoft blog, simplifies cloud-native operations further. (Microsoft Open Source Blog)

Yet compatibility remains the headline feature. Popular MongoDB drivers and tools work with minimal or no code changes. Aggregation pipelines, including $lookup operations, execute through the translation layer. Recent community analysis by Franck Pachot on dev.to explores how the planner chooses between nested-loop and hash-join strategies for $lookup based on BSON document flexibility. The trade-offs reflect the hybrid nature of the engine. (dev.to, June 2026)

So what does this mean for production workloads? Teams that already run PostgreSQL gain a document interface without spinning up another database cluster. Organizations wary of proprietary managed services now have a fully open alternative. And the timing aligns with surging demand for AI applications.

DocumentDB stores embeddings directly inside BSON documents alongside metadata and source text. Vector search uses HNSW and IVFFlat indexes powered by pgvector. Queries combine similarity search with metadata filters in a single aggregation pipeline. No separate vector store. No synchronization layer. No extra points of failure.

The AI page on documentdb.io contrasts the typical fragmented stack—application database, dedicated vector database, constant syncing—with the consolidated model. “Documents, vectors, and search in one Mongo API-compatible system.” Retrieval-augmented generation becomes simpler. Semantic search, agent memory and knowledge navigation all benefit from co-located data and unified querying. Geospatial, graph and full aggregation capabilities ride along for free. (documentdb.io/ai)

Microsoft has also integrated the open-source engine into its cloud offerings. Azure Cosmos DB for MongoDB (vCore) was renamed Azure DocumentDB in late 2025. The service now builds on the same open project, promising customers a migration path that preserves openness while adding managed scale. Service-managed regional failovers reached general availability in June 2026, automatically promoting replicas and updating connection strings with zero manual intervention. (Microsoft devblogs, June 2026)

AWS continues developing its own Amazon DocumentDB managed service. That product remains closed-source and tied to AWS infrastructure. The open DocumentDB project, by contrast, runs anywhere. The distinction grows sharper as enterprises demand multi-cloud flexibility and avoid vendor lock-in.

Industry reaction has been positive but measured. Supabase, Ubicloud, SingleStore and Cockroach Labs each issued supportive statements when the Linux Foundation announcement dropped. Spencer Kimball, co-founder and CEO of Cockroach Labs, highlighted PostgreSQL’s extensibility. “PostgreSQL has withstood the test of time because of its tremendous versatility and extensibility. That includes document database capabilities, and the open source DocumentDB project makes that extremely simple for developers already familiar with MongoDB.” (Linux Foundation press release)

Paul Copplestone, CEO of Supabase, pointed to future innovation. “The DocumentDB project enriches Postgres with first-class support for BSON, and provides simple hooks via a Postgres extension. DocumentDB joining the Linux Foundation is a strong commitment to the open source and developer community.” (Linux Foundation press release)

Questions remain. Performance at massive scale compared with tuned MongoDB clusters still needs independent benchmarks. Query optimizer behavior on highly variable BSON documents continues to evolve. Governance under the Linux Foundation will determine whether contributions stay balanced or tilt toward any single vendor.

Even so, the project has already changed the conversation. Developers no longer must choose between document ease and relational strength. They can have both. And they can run it on their own infrastructure, under an open license, with a growing community steering its direction.

The next phase will test whether DocumentDB can convert early excitement into widespread production adoption. Recent activity—improved aggregations, better cursor support, Kubernetes operator enhancements—suggests steady progress. With PostgreSQL’s ecosystem at its back and the Linux Foundation’s neutral ground beneath it, the database has a foundation few competitors can claim.

Subscribe for Updates

DatabaseProNews Newsletter

The DatabaseProNews Email Newsletter is a must-read for DB admins, database developers, analysts, architects, and SQL Server DBAs. Perfect for professionals managing and evolving modern data infrastructures.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us