Lesson 10 of 12 intermediate

Production operations, accessibility and rollback

Deploy সফল মানে command শেষ না। ব্যবহারকারী কাজ করতে পারছে, fail করলে ফিরে আসা যাচ্ছে কি না দেখো।

Guess first

Pick an answer. You will see if you were right at the end of the lesson.

Did authentication, ticket sync and review work?

Open interactive version (quiz + challenge)

Real-world analogy

Opening a shop includes the fire exit, inventory record and a plan for power cuts.

What is it?

A release includes a reproducible artifact, observable behaviour, health checks and a rollback path. For mobile clients, server compatibility matters because users update slowly. An accessible error and offline recovery path are part of correctness.

Real-world relevance

One shared support-ticket product, three optional entry points. Frontend: Rehearse reverting a web build and check keyboard navigation on the deployed version. Backend: Rehearse an API rollback without invalidating the database or older clients. Mobile: Plan server compatibility for old app versions and verify the store-release journey.

Key points

Use synthetic staging — Demonstrate the capstone without copying customer or employer data.
Keep compatibility — Older mobile clients must understand new backend responses or fail safely.
Observe outcomes — Record request ids, latency, failure category and model version without raw private ticket bodies.
Set stop signals — Decide which error or privacy failures block rollout.
Exercise rollback — Document the previous artifact and handle data migrations separately.
Test accessibility — Use keyboard navigation, screen-reader labels and readable loading/error states.
Verify from outside — A deploy command succeeding is not proof the live user journey works.
Frontend practice — Rehearse reverting a web build and check keyboard navigation on the deployed version.
Backend practice — Rehearse an API rollback without invalidating the database or older clients.
Mobile practice — Plan server compatibility for old app versions and verify the store-release journey.

Quick check

Answer from memory — scrolling up first makes it stick less.

What artifact demonstrates this lesson?

Which statement is defensible?

Code example

Release record
- source commit:
- artifact checksum:
- tests and environment:
- compatible client versions:
- synthetic smoke journey:
- rollback artifact:
- rollback rehearsal result:
- unresolved risks:

Line-by-line walkthrough

1. This release template intentionally has empty evidence fields. Fill them from actual runs. An empty rollback rehearsal field means the release gate is incomplete.

Spot the bug

200 OK from homepage means all workflows are healthy

Need a hint?

Did authentication, ticket sync and review work?

Show answer

Run an authorised synthetic end-to-end journey and verify the critical boundaries.

Explain like I'm 5

Fun fact

A useful artifact for this lesson: Demonstrate the capstone without copying customer or employer data.

Hands-on challenge

Choose ONE stack; you do not need to build all three. Junior foundation: Deploy only synthetic data to a sandbox and document a smoke test. Senior extension: Rehearse rollback, backward compatibility, observability and incident response. Evidence: save the input, expected behaviour, actual result and one failure or limitation. Junior means basic coding and Git, not zero programming experience.

More resources

Building effective agents (Anthropic)
Download the free offline lab (Python, tests and instructions) (Teamz Lab)

Open interactive version (quiz + challenge) Download the whole course as PDF / Word

Lock it in

← Back to course: AI-Assisted Software Engineering