8.11 Lab — design badge API pipeline on paper
Lab
Design (paper, whiteboard, or markdown note — no need to automate yet) a pipeline for Instagram-style badge API.
- List stages: lint, test, build, push, deploy-staging, approve, deploy-prod.
- For each stage write: trigger (PR vs main), what must be green, artifact produced (if any).
- Mark one fail-fast stage that should run first.
- Write the image tag scheme you will use (include git SHA idea).
- Write rollback: "If prod health fails, redeploy tag ____."
- Note where secrets will live later (not in Git) — one sentence.
- Keep the page — you will turn parts of it into GitHub Actions next chapter.
Practice task
Explain in five lines to a project manager: why the conveyor stops when a test fails, using badge API peak traffic as the story.
Thodkyaat sangaycha tar
- CI verifies every change; CD is delivery and/or deployment depending on company language.
- Typical stages: lint → test → build → push → deploy (staging then prod).
- Promote the same versioned artifact; avoid mystery rebuilds on the server.
- Environments separate config and risk; staging rehearses before production.
- Fail fast + quality gates; manual prod approval when risk or learning demands it.
- "CI green" is necessary but not always sufficient for a safe prod push.
Samajla ka? Nasel tar lab (8.11) pipeline paper punha clear kara – stages, tag, rollback. Aata pudhe jaauya GitHub Actions hands-on kade.