9 — CICD, Deployment Workflows & Observability

1 E N G I N E E R I N G D E L I V E R Y T R A C K CI/CD, Deployment Workflows and Observability From branching discipline to error budgets — the why, the trade-offs, then the how. By Md Ahbab Hamid Khan

O R I E N TAT I O N 2 How to read this deck Structure, conventions and what is deliberately out of scope. ■ Seven numbered sections, each opened by a divider slide. ■ Every practice states the failure it defends against. ■ Trade-offs come first; configuration and commands come second. ■ Code samples are runnable and captioned with their file path. ■ Comparison tables appear wherever competing tools are equivalent. ■ No long hands-on labs — reference depth, not workshop depth.

O R I E N TAT I O N 3 Assumed prerequisites What this deck takes as already known, and what it will define. ■ Fluency in at least one programming language and its package manager. ■ Comfort with functions, classes, and asynchronous execution models. ■ Working knowledge of HTTP: methods, status codes, headers, TLS. ■ Everyday Git: clone, branch, commit, merge, rebase, remote. ■ Basic shell usage and reading a Linux process or log. ■ No prior CI/CD, container, or cloud experience is assumed.