Microsoft is making a strategic move into the NoSQL database market with the introduction of open-source extensions for PostgreSQL, aimed at supporting document-style data and enhancing compatibility with MongoDB. The move underscores a broader industry trend where relational and non-relational databases are converging, blurring the lines between traditional SQL and schema-less database models.
Microsoft’s Open Source PostgreSQL Extensions
Last month, Microsoft announced the development of two new extensions for PostgreSQL:
- pg_documentdb_core – A custom extension enabling support for BSON (Binary JavaScript Object Notation), the format used by MongoDB for document storage.
- pg_documentdb_api – A data layer that provides MongoDB-compatible commands for CRUD operations (Create, Read, Update, Delete), query execution, and index management.
These extensions are set to run on Azure Cosmos DB for PostgreSQL, Microsoft’s cloud-based managed database service, but can also be used with FerretDB, an open-source alternative to MongoDB.
Microsoft’s decision to expand PostgreSQL capabilities highlights its ongoing commitment to open-source technologies, despite historically relying on proprietary software. The company has become a significant contributor to PostgreSQL, and this latest initiative reinforces its strategic push into the NoSQL space.
A Shift in the NoSQL Landscape?
According to Andrew Pavlo, a database expert and associate professor at Carnegie Mellon University, the distinction between relational (SQL) and non-relational (NoSQL) databases is rapidly diminishing.
“The intellectual distance between document/JSON DBMSes and relational DBMSes is shrinking. At some point, the two system categories will be indistinguishable (at least in terms of the data model),” Pavlo told The Register.
He noted that many NoSQL systems are evolving toward relational database structures, with key-value stores like Redis being the main exception. Several NoSQL platforms, including Cassandra (CQL) and Aerospike (AQL), now offer SQL-like interfaces while maintaining NoSQL characteristics. Even MongoDB integrated SQL support into its Atlas service in 2022, further signaling this shift.
The PostgreSQL community has been steadily enhancing JSON document support since 2013, but Microsoft’s new extensions take this integration further, bringing PostgreSQL much closer to MongoDB’s capabilities.
MongoDB’s Response: Dismissing Microsoft’s Efforts
Unsurprisingly, MongoDB was not impressed by Microsoft’s push into its domain.
A MongoDB spokesperson criticized the approach, stating:
“The rise of MongoDB imitators proves our document model is the industry standard. But bolting an API onto a relational database isn’t innovation – it’s just kicking the complexity can down the road. These ‘modern alternatives’ come with a built-in sequel: the inevitable second migration when performance, scale, and flexibility hit a wall.”
The comment underscores MongoDB’s confidence in its native NoSQL design, arguing that retrofitting document database functionality onto PostgreSQL will ultimately lead to performance and scalability challenges.
FerretDB’s Role and Microsoft’s Long-Term Vision
FerretDB, an open-source MongoDB alternative, is playing a key role in Microsoft’s initiative. The PostgreSQL-based project aims to provide a drop-in replacement for MongoDB while maintaining full open-source transparency under the Apache 2.0 license.
FerretDB CEO Peter Farkas confirmed that his company is working with Microsoft to create a stronger alternative to MongoDB, but he also emphasized that the ultimate goal is collaboration among multiple PostgreSQL-based NoSQL solutions.
“The goal with this is to work broadly among the providers of MongoDB alternatives and have more cooperation. After a while, they would have one solid foundation for MongoDB alternatives, which everybody could build on,” Farkas said.
He noted that PostgreSQL’s extension ecosystem makes it easier to add NoSQL features without modifying PostgreSQL’s core. While PostgreSQL has supported JSON for years, it lacks the full feature set required to replicate MongoDB’s performance and functionality—something FerretDB aims to bridge with its document database layer.
Industry Perspective: A Serious Challenge or Just Another Competitor?
Industry analysts remain skeptical that Microsoft’s involvement with FerretDB signals a broader open-source strategy beyond its continued investment in PostgreSQL.
Gartner senior director Aaron Rosenbaum said that while Microsoft has heavily invested in PostgreSQL, it has no track record of supporting other open-source database projects. He sees the move as an extension of Microsoft’s existing PostgreSQL contributions rather than a radical departure from its strategy.
Henry Cook, Gartner director analyst, added that while Microsoft’s PostgreSQL enhancements will strengthen PostgreSQL’s market position, MongoDB is unlikely to be significantly impacted.
“MongoDB has established itself in a firm position within the market championing the NoSQL approach. This will provide more competition, but there are already other NoSQL offerings out there. MongoDB will continue to defend its position based on its merits,” Cook said.
Despite Microsoft’s efforts, MongoDB remains the dominant player in the document database market, backed by enterprise customers like Wells Fargo, Sega, and L’Oréal.
Microsoft’s NoSQL Ambitions: What’s Next?
Microsoft’s PostgreSQL extensions represent a strategic move to attract NoSQL developers to its ecosystem while reinforcing PostgreSQL’s versatility.
While MongoDB remains a dominant force, Microsoft’s support for FerretDB and document-style PostgreSQL extensions signals growing industry momentum toward unifying SQL and NoSQL capabilities.
The big question is whether developers will embrace Microsoft’s NoSQL-on-PostgreSQL approach or stick with purpose-built solutions like MongoDB. Regardless of the outcome, the battle for NoSQL dominance is far from over.
Source: The Register
