Two options to deal with the "scary" part of big integrations in continuous deployment: Don't. Commit early, often and in small chunks. Just search for Continu

Two options to deal with the "scary" part of big integrations in continuous deployment: Don't. Commit early, often and in small chunks. Just search for Continuous Integration, more than enough has been said on it already. When you must, roll out features independently of the code being live in production. This means things like using control logic to roll out the code to portions of users, intelligently. We roll out via: on/off switches (mitigate total failure), A/B tests (mitigate poor performance in front of customers), QA-rollout (mitigate bad experiences for customers), etc. Lots of flexibility here, including hidden rollouts: running the code without showing the results to users, so you can figure out scalability impacts.