Moving MongoDB Workloads to Postgres with FerretDB
summary
FerretDB claims it lets MongoDB applications run unchanged on Postgres by translating the MongoDB wire protocol into SQL and shipping under Apache 2.0, turning Postgres (and SQLite, SAP HANA, cloud Postgres providers) into a MongoDB-compatible layer. Independent tests show roughly a 50% performance gap versus MongoDB Atlas today but the project reports production readiness and over 1,000 migrations underway. The thing built is a standalone proxy that accepts MongoDB drivers, issues SQL to the backend, and works well enough to replace embedded or cloud MongoDB deployments without application rewrites.
AI-written summary · about
chapters (9)
- 0:00MongoDB and FerretDB intro
- 1:08Why MongoDB is not open source anymore
- 6:51SQL history overview
- 14:26MongoDB’s proprietary shift
- 21:39FerretDB as MongoDB alternative
- 26:48FerretDB architecture and backends
- 27:53Performance benchmarks and compatibility
- 29:58FerretDB adoption and use cases
- 30:41Conclusion and call to action
related talks
43mFerretDB — mongoDB on the outside, PostgreSQL on the inside
42mFrom MongoDB to Postgres: Building an Open Source Standard for Document Databases
24mBuilding an open-source MongoDB-compatible database on top of PostgreSQL
32mFrom MongoDB to Postgres: Building an Open Standard for Document Databases
04mDave Stokes Talks Open - Episode 5
15mFrom MongoDB to Postgres: Building an Open Source Standard for Document Databases
45mBuilding an Open Source MongoDB-compatible Database on Top of PostgreSQL
29mSwitching to MongoDB: The challenges of translating database schemas