Microsoft has announced the launch of DocumentDBa new documentary database (DDB) open source database built on PostgreSql. This initiative seeks to provide the developer community with an interoperable and portable Nosql solution, taking advantage of the lack of common standards in this area.
Microsoft Open Source Blog tells that Documentb was born with the mission of offering a local instance, ready for production, that is fully compatible and backed by an active community. That is, quite the opposite of what, historically, has happened with this type of solutions, usually linked to specific cloud solutions, with interoperability handicaps and portability between different platforms.
An example of this would be Amazon Documentb, a private DDB system compatible with the referent of its category, Mongodb, part of the AWS offer. Microsoft Documentb does not deceive with the name, but has chosen to do it otherwise, with the focus on Azure Cosmos DB for Mongodb, but under the open source model. Specifically, the license chosen has been the MIT.
In such a panorama, the doubt of What happened to Mongodb To reach this point and the answer is none other than the Free riding and the change of Mongodb license, which in turn caused the contempt of the project by many great actors in the industry. Thus, in Microsoft they have opted to lift their documentDB about PostgreSql, an open database system, known for its robustness and versatility.
Those responsible that one of the key DocumentB objectives is to provide developers a complete vision of the architecture and implementation of the database, so the basic components of the system, from the crud operations (create, read, read, Update, eliminate) until indexation and vector search functionality are public and accessible. The MIT license makes the rest, since the user of the software does not force.
Microsoft’s clear intention with DocumentDB is the Proposal for a kind of standard for open source document databasessimilar to the ANSI SQL standard for relational databases: minimize differences in public APIs and engine foundations between different NOSQL database implementations, thus facilitating more friendly adoption and better experience for developers when using different DDB systems.
On the other hand, Microsoft wants to do things well and not only encourages the community to participate in the development of Documentb; He will do the same with PostgreSql, they say, giving first hand. After all, without postgresql there would be no documentdb and the purpose is that a project continues to feed on the other, so that it is also essential to guarantee the good health of the first.
