From MongoDB to Postgres: Building an Open Standard for Document Databases
summary
MongoDB’s 2018 switch to SSPL creates vendor lock-in; a 67K-developer StackOverflow survey still shows Postgres as the most wanted DB. The claim: run MongoDB workloads on Postgres without app changes by using FerretDB, an Apache 2.0 Go compatibility layer that accepts standard MongoDB drivers and stores data in Postgres. FerretDB 2.0 aligns with Azure Cosmos DB for MongoDB, proving cross-implementation compatibility, and the community-led OpenDocDB effort aims to certify a common MQL core for migrations and service offerings.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:28Why move MongoDB to Postgres?
- 4:42MongoDb's licensing
- 7:43Why not Just Use Postgres & JSON?
- 9:38History of SQL as an Open Standard
- 16:29History Repeats Itself… Sort Of
- 21:08MongoDB Query Language as an Open Standard
- 23:00Architecture of FerretDB
- 30:32Conclusion
related talks
42mFrom MongoDB to Postgres: Building an Open Source Standard for Document Databases
15mFrom MongoDB to Postgres: Building an Open Source Standard for Document Databases
24mBuilding an open-source MongoDB-compatible database on top of PostgreSQL
32mMoving MongoDB Workloads to Postgres with FerretDB
43mFerretDB — mongoDB on the outside, PostgreSQL on the inside
45mBuilding an Open Source MongoDB-compatible Database on Top of PostgreSQL
53mPostgres vs Mongo
04mDave Stokes Talks Open - Episode 5