We've got a great discussion lined-up. Please come prepared to share your experiences and learn from others!
6:30-7:00: meet, greet, & eat
7:00-7:15: welcome, announcements, & introductions
7:15-9:00: discussion on designing data migrations
Designing Data Migrations in MongoDB - Jason Wieringa (@jwieringa) -
A few months ago you shipped a feature for your customers using embedded documents in a collection. Feedback has come back and with what you've learned you'll be making a feature change. The change is best served by making that embedded document into it's own collection and you must migrate customers existing data to the new collection. What is the best way to do this?
You've inherited an application using MongoDB. You notice a performance issue and you start digging into it, "25 separate calls to the database to build one html page? Why?" Alas, your MongoDB database is designed like a relational database - it's been normalized too much. You decide it's time to start changing the data schema, but where do you start?
What are the best practices when it comes to transforming data to new structures? Do you transform your data all at once? Do you transform it gradually each time the data is touched? What about never transforming it by including a feature switch that knows both data schemas?
Come join a discussion where we'll discuss current recommendations, new ideas, your challenges, and what you've done to address schema changes in your application.
This meetup is being held at Logik in DC. See you there!