DocumentDB has undergone a remarkable transformation, originating as a Postgres add-on before blossoming into a standalone project. This evolution reflects a significant shift in the landscape of open document databases, particularly with its recent adoption by the Linux Foundation.
From PostgreSQL Extensions to a Full Project
DocumentDB’s journey began in 2024, initially as a pair of PostgreSQL add-ons designed to manage BSON data models and facilitate document queries. Within a year, it had matured into a standalone database, leveraging the reliability and extensive ecosystem of PostgreSQL while offering developers the flexibility associated with NoSQL systems.
The adoption of DocumentDB under the permissive MIT license marks a strategic move towards fostering broader community engagement. Bruce Momjian, a founding member of the PostgreSQL core development team, expressed enthusiasm about the collaboration between major players like Microsoft and AWS, stating, “It’s great that Microsoft, AWS, and others are joining forces to work on DocumentDB, an open-source implementation of a MongoDB-compatible API on top of PostgreSQL.”
Kirill Gavrylyuk, vice president at Microsoft, articulated the project’s vision succinctly: “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.” This dual identity—part relational engine and part document store—positions DocumentDB as an appealing option for developers seeking a unified interface.
However, some skeptics argue that simply layering document features onto PostgreSQL does not eliminate the inherent limitations of traditional relational systems. The transition of DocumentDB to the Linux Foundation has garnered support from industry giants such as Amazon Web Services and Google, signaling a rare moment of alignment among major cloud vendors. Adam Abrevaya, director of Amazon DocumentDB, remarked, “AWS is excited to contribute to the open-source DocumentDB project, now stewarded by the Linux Foundation.” Similarly, Sailesh Krishnamurthy, vice president of engineering at Google Cloud, noted, “It is great to see the DocumentDB project joining the Linux Foundation, which assures customers and the community have an openly governed, open-source option available to them.”
Despite this backing, critics caution that vendor neutrality can often be more symbolic than substantive. A project supported by hyperscalers risks being influenced by their priorities, potentially sidelining smaller contributors and raising questions about the genuine influence of community governance.
The rise of DocumentDB can also be interpreted as a direct response to MongoDB’s shift towards restrictive licensing models. By presenting a permissive alternative, the Linux Foundation aims to promote a more interoperable standard for document databases. Industry veterans contend that such a standard is long overdue, although the timing remains contentious. MongoDB continues to hold a dominant position in the market, with proponents arguing that merely adding document capabilities to PostgreSQL cannot replicate the advantages of a native design.
Jim Zemlin, executive director of the Linux Foundation, emphasized the importance of DocumentDB in the ecosystem, stating, “DocumentDB fills a critical gap in the document database ecosystem, attracting contributors, users, and champions. It provides an open standard for document-based applications.” For developers engaged with Linux distributions or configuring laptops for programming, DocumentDB may present itself as yet another tool promising simplicity and openness.
Enterprises exploring mobile workstations or SaaS integrations may also find value in a standardized, Postgres-based NoSQL option. Nevertheless, the path to success hinges on the technical merit of DocumentDB and the community’s ability to resist the gravitational pull of the largest vendors in the space.
