From MongoDB to Postgres: Building an Open Source Standard for Document Databases
summary
Claims that Postgres can act as an open-source backbone for MongoDB workloads, using FerretDB as a compatibility layer that accepts MongoDB drivers unchanged and translates them to SQL on Postgres as storage engine. Uploader-backed work is Apache 2.0 and includes a Microsoft-contributed engine; implementation works functionally but incurs a workload-dependent performance penalty (sometimes close to parity, sometimes much worse). Existing MongoDB tools can connect and Postgres tables remain queryable via SQL.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:31Moving from MongoDB to Postgres
- 9:02Risks of non-open-source databases
- 14:49SQL and open standards history
- 21:43MongoDB licensing shift
- 26:40Problems with MongoDB alternatives
- 31:51Postgres solves MongoDB dilemma
- 35:09Key takeaways
- 37:05Q&A
related talks
32mFrom MongoDB to Postgres: Building an Open Standard for Document Databases
15mFrom MongoDB to Postgres: Building an Open Source Standard for Document Databases
32mMoving MongoDB Workloads to Postgres with FerretDB
24mBuilding an open-source MongoDB-compatible database on top of PostgreSQL
43mFerretDB — mongoDB on the outside, PostgreSQL on the inside
45mBuilding an Open Source MongoDB-compatible Database on Top of PostgreSQL
04mDave Stokes Talks Open - Episode 5
04mGetting Started with DocumentDB and Open Source