News for hackers. Stuff that matters.
Re:A behind-the-scenes look at Facebook release engineering by raphinou on Thursday April 05, 2012 @12:04PM (#3803173)
The article mentions that employees visiting Facebook from inside use an experimental build. Any idea how they manage this if the experimental build requires changes in the data structures used by the site?
Re:A behind-the-scenes look at Facebook release engineering by HarrisonFisk on Thursday April 05, 2012 @02:42PM (#3803947)
Re:A behind-the-scenes look at Facebook release engineering by bonzoesc on Thursday April 05, 2012 @12:29PM (#3803322)
I suspect that if new features require storage changes, the changes are strictly additive and won't affect old features, or old features are modified to use the new storage setup.

With the amount of data Facebook has, they probably don't have the option of an "iterate over every row and change a thing" kind of migration.

Re:A behind-the-scenes look at Facebook release engineering by flyt on Thursday April 05, 2012 @12:50PM (#3803420)
No, but they do have an extremely fast and efficient tool for performing online schema changes to its huge MySQL deployment: https://www.facebook.com/notes/mysql-at-facebook/online-sche...
Re:A behind-the-scenes look at Facebook release engineering by ahupp on Thursday April 05, 2012 @03:00PM (#3804045)
Eventually you'll have users in the same state, either because the push is not atomic or because the change is rolled out slowly. This means you have to build the change with this in mind regardless of the employee testing.