Re:A behind-the-scenes look at Facebook release engineering
by sciurus on Thursday April 05, 2012 @11:32PM
(#3805869)
jpeterson didn't suggest "installing a bunch of libraries and updating things piecemeal". Instead of transferring the entire binary for every release they could generate a (likely much smaller) patch, transfer just it, then apply it. I expect they're not doing this because it's computationally intensive compared to transferring the entire binary.
The reason why people tend to gravitate to incremental deployments for web applications is because the typical tools encourage it; modules get installed in separate directories, each part of the app is a separate file (back in the CGI days), etc. When you compile everything into one file, though, then you just copy that file around to deploy. It's easier. (Ask a PHP programmer how to change one file, and it will probably be "change that one file". Ask a Java programmer, and it will be "fix the file, build a WAR, and replace the WAR". Tools dictate process, and the "scripting language" default is to work on a file level instead of an application level.)
I've always wanted one-file deployment for my personal applications, but I never saw anyone doing it so I assumed I was wrong. But nope, it turns out that everyone else was wrong :)