Do's and Dont's of the modern hybrid mongoDB MySQL environment
summary
Recommendation: choose mongoDB for document workloads and MySQL for highly relational data, test MyRocks or InnoDB and MySQL partitioning for high write OLTP, and prefer built‑in horizontal scaling over ad hoc sharding. Avoid co‑hosting both on one OS or box, use hidden secondaries and secondary‑preferred reads for analytics, treat non‑native replication as an ETL workflow not real‑time sync, and add proper caches and queues like RabbitMQ or ZeroMQ. Use the right tool for the job.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:21Choosing the right database
- 1:48Use cases before selection
- 3:14Scaling databases
- 5:03Consistency models
- 7:54Deploying MySQL and MongoDB
- 10:01Replication pitfalls
- 11:26Joins: when to use
- 12:08Caching and logging
- 13:33Key takeaways
related talks
53mMySQL DevOps
44mMongoDB to MySQL the How and the Why
25mHybrid Applications with MongoDB and RDBMS
27mMurdering our Mongo Database (or how we migrated to a relational database)
35m10 things a developer should know about databases
25mData in the Cloud
38mFrom Tables to Documents—Changing Your Database Mindset
24mComparing the High Availability of MySQL with Modern Distributed SQL Databases