Continuous Deployment

Reducing the delay

Between the time a developer commits code to the repository and the time it runs in production, code is a pure liability. Undeployed code is unfinished inventory. It has unknown bugs. It may break scaling or cause production downtime. It might be a great implementation of a feature nobody wants. Until we push it to production, we can’t be sure. The idea of continuous deployment is to reduce that delay as much as possible to minimize the liability of undeployed code.

Deployment size and risk

A vicious cycle is at play between deployment size and risk, too. Look at the figure below.