News for hackers. Stuff that matters.
Re:A behind-the-scenes look at Facebook release engineering by bonzoesc on Thursday April 05, 2012 @01:42PM (#3803652)
> The binary executable is just one part of the Facebook application stack, of course. Many external resources are referenced from Facebook pages, including JavaScript, CSS, and graphical assets. Those files are hosted on geographically distributed content delivery networks (CDNs).

It doesn't say whether or not these are part of the binary, but I'd suspect they aren't used as the CDN origin. You'd want these (randomly-but-uniquely named) resources to be pushed out to the CDN and warmed up before a deploy to avoid a thundering herd[1] problem from millions of users.

1: http://en.wikipedia.org/wiki/Thundering_herd_problem

Re:A behind-the-scenes look at Facebook release engineering by nbm on Thursday April 05, 2012 @02:00PM (#3803743)
Ignoring technical ways to work around the thundering herd problem, the slow rollout (employees first for several days, then a subset of servers, then a larger subset) also mitigates the problem.