addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

May MongoDC Meetup

  • May 15, 2013 · 6:30 PM

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 MongoDBJason 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!

 

 

 



 

 

Join or login to comment.

  • Joey M.

    Good presentation that sparked good discussion!

    May 15, 2013

  • A former member
    A former member

    Fantastic

    May 15, 2013

  • A former member
    A former member

    Great meetup everyone. I had to duck out early to meet my family.

    I look forward to meeting with you all next month!

    See you then if not before.

    - Rob

    May 15, 2013

  • Kha t.

    I come late. can someone help me get to 8th floor. I am at elevator 1st floor

    May 15, 2013

  • Nathen H.

    May 15, 2013

  • David B.

    Mentioned in tonight's meetup, Ted Neward's legendary article about ORMs being the Viet Nam of computer science.

    http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx

    If you want to skip the history lesson, the point relevant to tonight's meetup is the section labelled 'the object relational impedance mismatch'.

    1 · May 15, 2013

  • Christopher S.

    Can someone let us in? :-)

    May 15, 2013

  • A former member
    A former member

    I got pulled away on travel. Sorry to miss it.

    May 13, 2013

  • Jonathan A.

    Whoops, out of town for this month's meetup

    May 8, 2013

52 went

Our Sponsors

  • Snagajob

    Meeting space, Speakers, Pizza, and refreshments

  • Make|Office

    meeting space

  • MongoDB

    Speakers, beer, pizza, and MongoDB, of course.

  • Fluencia

    Meetup hosting, pizza, beer, and recording services.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy