At the recent Open Source Summit Europe, the Linux Foundation announced an exciting new project called DocumentDB. This database is compatible with MongoDB but built on PostgreSQL, aiming to make it easier for developers to deploy and query data. The project was first announced by Microsoft early in 2025 and is now part of the Linux Foundation’s open source ecosystem. With more options available, choosing the right document database can be more confusing than ever for developers and organizations alike.

Why Choose a Document Database?

Document databases store data in a flexible format that’s easy to work with, often using JSON. This makes them a popular choice for developers who aren’t familiar with the complexities of relational databases or who need to adapt their data schemas over time. Because of this flexibility, they’re ideal for rapid prototyping and agile development projects.

MongoDB is a prime example of a successful document database. It has attracted over 59,000 customers and has become a go-to tool for developers looking to build quickly without worrying about rigid schemas. Over the past decade, other companies have launched their own document database solutions, and there are also services compatible with MongoDB’s API. The addition of DocumentDB as a Linux Foundation project brings even more options into the mix.

Deciding How to Deploy Your Database

When it comes to deploying a database, there are two main decisions: what technology to run and how to run it. The first involves choosing the right database for your needs, while the second is about selecting the deployment method. You can run databases on your own hardware, in the cloud, or through managed services.

Running your own instance gives you full control but requires more resources and expertise. Cloud hosting options allow you to manage the software while the provider takes care of infrastructure. Managed services go a step further by handling most of the operational tasks, letting your team focus on development. Each approach has its benefits and trade-offs, especially when considering speed, control, and costs.

However, it’s important to think about vendor lock-in. Using cloud services can tie you to a provider’s ecosystem, making migration difficult and potentially expensive if prices increase or if you want to switch providers later. Balancing the need for quick deployment with long-term flexibility is key to choosing the right infrastructure approach for your project.

Inspired by

• https://www.infoworld.com/article/4089472/document-databases-understanding-your-options.html

Sources

• linuxfoundation.org
• github.com
• percona.com
• documentdb.io
• microsoft.com