All visualizationsSystem Design · 10 of 34
CI/CD — the journey of one commit
Push → fresh build → the test wall → one sealed image → staging → a canary into production. Including the commit that never made it.
💡
THE BIG IDEA
Between "it works on my laptop" and "10,000 users have it" stands a pipeline: every push gets built from nothing on a fresh machine, judged by every test the team ever wrote, sealed into one image, rehearsed on staging, and eased into production behind a canary dial. This theatre follows one commit through all of it — and stages the moment that justifies the whole machine: the broken commit whose bug dies on a disposable runner instead of in production.
Press ▶ Play to watch it run step by step, or use the arrow buttons to go at your own pace.
1
Two teams. One merges to main weekly in a giant, terrifying "integration day". The other ships small commits that flow to production the same afternoon — calmly. The difference is not talent. It is a pipeline.
CI/CD is the machinery that makes the second team possible: every push is integrated, built, tested and made deployable — automatically, every time.
🧑‍💻You — git push
📚Repository (main)
handling requestjust addedDOWNunder loadhealthy
1/11
UP NEXT IN SYSTEM DESIGN
Consistency & Quorums — One Balance, Three Copies
W+R > N overlap, read repair, and the CAP choice when the cable is cut
CDN — Content Close to the UserConsistency & Quorums — One Balance, Three Copies