Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Matthew Borden This is the story of migrating large parts of an application’s data layer from MongoDB to MySQL with zero downtime using Ruby. We’ll cover designing schemas to represent untyped data, dual writing to both databases, migrating old data and staging the cutover to the new database. Matthew is a Site Reliability Engineer at Seer Medical maintaining a cloud based epilepsy diagnostics system. Previously, he was at Stile Education developing a science education platform for high school students. He enjoys the detective work of debugging issues in production, the delightful nature of writing Ruby and finding new ways to break systems early before they break in production. Produced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub_confirmation=1 #ruby #rubyconf #rubyconfau #rubyconf_au #rails #programming Fri Feb 21 10:00:00 2020 at Plenary Room
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the talk titled "Murdering our Mongo Database (or how we migrated to a relational database)", Matthew Borden, a Site Reliability Engineer at Seer Medical, shares about the migration of an application’s data layer from MongoDB to MySQL without downtime. Borden explains the challenges and learnings from this process, highlighting several key points: - **Background of the Project**: The project originated at Stile Education, where the application initially utilized MongoDB due to its perceived advantages over MySQL at the time. However, as the application evolved, issues surfaced that made MongoDB less suitable for their needs. - **Issues with MongoDB**: Borden discusses various trade-offs of using MongoDB, such as lack of schema enforcement, complexity in managing two databases, and recurring outages that negatively impacted the application’s reliability. - **Decision to Migrate**: The lack of a true technical need for a second database prompted the decision to migrate from MongoDB to MySQL, allowing the team to streamline their tech stack by focusing on one reliable database. - **Migration Strategy**: The migration implemented a dual-writing approach, where data was written to both MongoDB and MySQL simultaneously. Borden emphasizes the importance of performing tests concurrently to ensure data consistency and integrity throughout the transition. - **Use of Tools**: To aid in the migration, Borden refers to tools like Scientists for testing accuracy and Yaeger for monitoring API requests, ensuring that all dependencies on MongoDB were identified and addressed. - **Conclusion**: The successful migration led to the complete removal of MongoDB from the application, simplifying the architecture and eliminating the complexities associated with dual databases. Borden stresses the importance of evaluating the technology stack to ensure it continues to meet application needs. Ultimately, Matthew Borden’s talk offers valuable insights into the practical challenges and solutions surrounding database migrations in software applications, underscoring the importance of maintaining a simplified and efficient tech stack.
Suggest modifications
Cancel
