Courting Mongo, committing to Postgres: Our data love story!
summary
Seven years on MongoDB Atlas turns into chronic duplication, chaotic nested documents and slow queries, so migration to Postgres begins: custom migration scripts (no off‑the‑shelf tool), two years of hybrid operation, and use of MongoDB Atlas TTL index for soft deletes during the transition. Developers build Docker database templates and Bitbucket pipeline tests to give everyone local copies; Postgres uses Postgres logical replication, pgcrypto and pgvector extensions, and mostly fixes consistency though an early replication mistake causes a multi‑hour outage.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 1:05Choosing a database like love
- 2:52Why we chose MongoDB
- 8:36Problems with MongoDB
- 16:13Why we switched to PostgreSQL
- 18:19Challenges migrating to PostgreSQL
- 21:10Lessons learned and conclusion
- 22:34Q&A session
related talks
29mSwitching to MongoDB: The challenges of translating database schemas
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
43mCRIMS: The case of the DB change that left no trace
26mMastering Large-Scale PostgreSQL Migration
46mBig databases, many servers, data center or cloud - it's all here!
32mFrom MongoDB to Postgres: Building an Open Standard for Document Databases
36mTales from the Postgres Front, and What We Can Learn
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL