Part 0 · 1 chapters · ~8 min
From scp to Pipelines
How deploying evolved from copying files to immutable artifacts, continuous deployment and progressive delivery, and the vocabulary used for the rest of the course: build, artifact, deploy, release, rollout, rollback.
1
The history and the vocabulary
| term | meaning |
|---|---|
| build | turn a commit into an immutable artifact (image, binary, bundle) with a version |
| deploy | run that artifact in an environment |
| release | expose the new behaviour to users (can be separate from deploy, via flags) |
| rollout | the controlled process of moving traffic or instances to the new version |
| rollback | return to the previous artifact; roll-forward: ship a fix instead |
| blast radius | the share of users or systems a bad change can reach before it is stopped |
HOW DEPLOYING CHANGED
each era removed a class of deploy failure
swipe the figure sideways, or tap expand for full screen
1/5
copying files
Deploys meant copying files onto live servers: half-updated servers, no rollback, and every server slightly different.
mutable servers, no rollback"works on server 3 only"