4 ms·
"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 contribu
by ironchef 15y ago
"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.
- MatthewPhillips 15y agoPresumably 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.
- rhizome 15y agoCGI?
- darklajid 15y agoI'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?
- HarrisonFisk 15y agoHPHP has a built in multi-threaded webserver.