#Microsoft #DocumentDB, la base de données open-source documentaire #NoSQL compatible #MongoDB et basée sur #PostgreSQL gagne du terrain dans le monde de l'#opensource : https://shorturl.at/Th8OM
Intéressant @Infodocs ?
#Microsoft #DocumentDB, la base de données open-source documentaire #NoSQL compatible #MongoDB et basée sur #PostgreSQL gagne du terrain dans le monde de l'#opensource : https://shorturl.at/Th8OM
Intéressant @Infodocs ?
#Microsoft releases #DocumentDB ( #NoSQL atop #Postgres ) under MIT license https://opensource.microsoft.com/blog/2025/01/23/documentdb-open-source-announcement/
DocumentDB, nueva BBDD documental de código abierto basada en PostgreSQL
https://www.muylinux.com/2025/01/30/microsoft-documentdb-codigo-abierto/
Microsoft releases #DocumentDB, an #OpenSource #NoSQL database backed by #PostgreSQL. This is what powers #Azure Cosmos DB for MongoDB. It's supported by FerretDB 2.0.
https://opensource.microsoft.com/blog/2025/01/23/documentdb-open-source-announcement/?WT.mc_id=DT-MVP-5003831
Wait, #Microsoft has released #DocumentDB as an #opensource native implementation of document-oriented NoSQL database within a PostgreSQL framework
https://github.com/microsoft/documentdb
Isn't it the same name that the AWS' Mongo-compatible service?
I'm thinking that regarding Doxstorr, granular control of ACID behaviour would make sense in the context of transaction execution and not so much on a per-query basis.
If anybody knows any document databases that let you have extremely granular control of ACID-ity, please let me know!
I'm working on rserv 0.3.8
https://github.com/ha1tch/rserv/blob/main/manual/rserv-manual-part5-graphs.md
Since 0.3.x rserv has incorporated certain graph-like features that allow you to query data from a property graph perspective.
Any document stored in rserv for any given entity can now be treated as a node from the graph-like perspective.
In order to perform graph queries, I added Sulpher, which is a funny name for a reduced subset of Cypher (the Neo4j query language).
Now I'm more happy with the general design (and keeping it RESTful! unlike GraphQL!) I think I will be ready to make the first public release soon.