Re:A behind-the-scenes look at Facebook release engineering
by ironchef on Thursday April 05, 2012 @12:49PM
(#3803418)
"Facebook is updating tens of thousands of servers with every push. "Rolling back" a release would effectively take as long as a regular push and could contribute to problems if they're found."
Absolutely not. A lot of places get around this with a simple symlink switch. You keep N older releases. So it might be /code/releases with various datestamped releases...and /code/releases/current points to the currently running one. Want to rollback? Point current to one older. Done.
[ Parent
| on HN ]
Re:A behind-the-scenes look at Facebook release engineering
by MatthewPhillips on Thursday April 05, 2012 @01:08PM
(#3803493)
Presumably the 1.5gb facebook binary is deployed as a daemon listening on port 80. Seems unlikely that they are cgi-ing a new process for each request.
Re:A behind-the-scenes look at Facebook release engineering
by rhizome on Thursday April 05, 2012 @02:20PM
(#3803843)
CGI?
Re:A behind-the-scenes look at Facebook release engineering
by darklajid on Thursday April 05, 2012 @03:47PM
(#3804268)
I'm torn. I understand your question, but yeah - what is that binary doing?
It is compiled PHP. Do they embed an http server? Do they talk fcgi with a well-known webserver, like - php would?
Re:A behind-the-scenes look at Facebook release engineering
by HarrisonFisk on Thursday April 05, 2012 @04:42PM
(#3804524)
HPHP has a built in multi-threaded webserver.