Open Source DocumentDB 1.0 Reaches General Availability

DocumentDB has shipped version 1.0, its first generally available release. The project is an open source, MIT-licensed document database built on PostgreSQL that speaks the MongoDB wire protocol, so most MongoDB drivers, tools and queries are intended to run without changes. Microsoft announced the effort early in 2025, and it joined the Linux Foundation a few months later with backing from AWS, Cockroach Labs, Google, Snowflake and Yugabyte. Renato Losio reported the milestone for InfoQ.
Architecturally, DocumentDB has two parts. A PostgreSQL extension supplies MongoDB API-compatible functionality inside the database, and a separate gateway translates MongoDB protocol requests into PostgreSQL calls. That design keeps the document model and PostgreSQL's storage and operational tooling in the same system, which is the core pitch: teams can keep familiar drivers and query patterns while running on a relational engine they may already operate.
Version 1.0 supports PostgreSQL 15 through 18 through container images, and Linux packages are available for PostgreSQL 17 and 18. The release includes a Kubernetes operator. The team framed the GA work around security and stability, together with fixes to indexing, aggregation and geospatial queries — the areas where an API-compatible database tends to diverge most visibly from the system it emulates.
The licensing is a deliberate contrast with MongoDB. DocumentDB's MIT license permits commercial use, modification and hosting without requiring disclosure of proprietary code, whereas MongoDB uses the SSPL. The team described this in a companion article on what to know before building, deploying and distributing with the MIT license. In practice, that difference matters most to companies that embed a database in a product or offer it as a managed service, since permissive terms reduce legal friction in those scenarios.
Naming remains a live complaint. The project maintains a disambiguation page covering the open source project, Azure DocumentDB and Azure Cosmos DB, but the community is unconvinced. A widely read Hacker News comment from user marifjeren asked the team to pick another name, noting that DocumentDB is already what people call Amazon DocumentDB. The overlap is largely with Amazon's service rather than the underlying engine, but the practical effect is search noise and confusion in architectural discussions.
On compatibility, Microsoft product manager Patty Chow argued that multiple open source document database implementations give developers more choice in deployment and infrastructure while preserving MongoDB driver and query compatibility. She noted that MongoDB gave developers a widely used way to work with document data and that familiar drivers and query patterns are worth preserving, with alternative implementations letting developers keep that knowledge while evaluating different storage and deployment approaches.
Community experience is more mixed. On Reddit, user 716green described compatibility between MongoDB and FerretDB as minimal compared with expectations, while praising Microsoft's support for FerretDB. The two projects are related but distinct: DocumentDB provides the PostgreSQL extensions and its own MongoDB-compatible gateway, while FerretDB is a separate project that uses the DocumentDB extensions as a backend and provides its own MongoDB-compatible interface. This means compatibility gaps can originate in either layer, which complicates troubleshooting for anyone running FerretDB on top of DocumentDB.
Early performance signals are mixed and provisional. Layerbase ran an initial YCSB comparison of FerretDB and the PostgreSQL-based DocumentDB and found DocumentDB delivered 20 to 33 percent higher read throughput, while FerretDB had lower tail latency for updates in mixed workloads; Layerbase noted the results are not conclusive. Separately, an open GitHub issue reports higher query latency in DocumentDB 1.0 than MongoDB 9.0.4 across several workloads, though those results have not been independently verified. For a 1.0, that is not alarming — compat layers commonly carry translation overhead — but it is a reason to benchmark against your own workload rather than rely on headline numbers.
The release notes cover upgrade paths and known issues. The project plans separate long-term support and development tracks, with its versioning policy still under discussion. That is a detail worth watching: LTS branches and a stated versioning scheme are what enterprises typically require before standardizing on a database.
Why it matters: teams that want MongoDB-style document access without MongoDB's SSPL terms, or that want document workloads to sit on PostgreSQL they already run, now have a generally available option with Kubernetes support and container images spanning PostgreSQL 15 to 18. The caveats are real — mixed and unverified benchmarks, a name that collides with Amazon's service, and a versioning policy not yet settled — so adoption should lean on your own compatibility and latency testing. My reading is that DocumentDB's strongest fit is organizations already invested in PostgreSQL operations; those purely chasing MongoDB's latest features will likely stay put for now.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
DocumentDB 1.0 is the first generally available release of the open source, MIT-licensed document database built on PostgreSQL, with compatibility for the MongoDB wire protocol. Most MongoDB drivers, tools, and queries work without changes. By Renato Losio