News for hackers. Stuff that matters.
Re:A behind-the-scenes look at Facebook release engineering by nbm on Thursday April 05, 2012 @01:37PM (#3803630)
This deployment of what's called "www" ("dub-dub-dub") is somewhat monolithic in the sense that it is large, but it is not really an "all-or-nothing" deployment. It is tested internally (for at least 2-3 days) by employees (engineers and non-engineers), and then on a subset of servers, a larger subset, and so on. Performance, error rates, interaction rates, and so forth are compared between the incumbent and new-hotness versions for a reasonably reliable indication of issues throughout the rollout. More on the www push at https://www.facebook.com/video/video.php?v=10100259101684977

Teams that run "services" (such as the one that powers the "typeahead" search bar at the top of Facebook) deploy their services separately, at whatever pace makes sense for them. These are almost never in tight lock-step with anything else, for the usual reasons.

Re:A behind-the-scenes look at Facebook release engineering by magicalist on Thursday April 05, 2012 @02:26PM (#3803864)
If a new release goes out every day, how is that tested internally for 2-3 days? Do employees get split across versions or are incremental changes rolled out much more frequently?
Re:A behind-the-scenes look at Facebook release engineering by brown9-2 on Thursday April 05, 2012 @02:48PM (#3803971)
Sounds like only the latter is being discussed: Facebook typically rolls out a minor update on every single business day. Major updates are issued once a week, generally on Tuesday afternoons.