CoursesBackend engineering from first request to production

Puzzle 16 · 17 of 18

What evidence earns a release?

Ship a change with tests, a recovery path and a capacity argument.

All puzzles in this course

The problem

Your change passes on your laptop. What would another engineer need in order to release it and recover if it fails?

See it

What evidence earns a release? Test Build once Verify Recover

Scroll sideways to see the full diagram.

  1. Run repeatable checks from a clean checkout.

    Step 1 of 4
  2. Record the artifact being promoted.

    Step 2 of 4
  3. Exercise the user-visible operation.

    Step 3 of 4
  4. Recover and verify the stored row.

    Step 4 of 4

The building block

Start from a clean checkout and run the contract and integration tests. Build the image once and record its identity. Promote the tested artifact with environment-specific configuration supplied at runtime. A readiness probe covers one dependency path. Add a real write and read to the smoke test. Estimate load using requests per second and measured time per request. At a steady ten requests per second and an average response time of half a second, about five requests are in flight on average. Use a load experiment to find when queueing, errors or response times increase. Keep the previous compatible version available for rollback.

Rehearse the failure the release gate claims to cover

At noon the independent backup contains river. At 12:05 the service acknowledges hill. At 12:10 the data disk fails. Restoring only the noon snapshot recovers river and loses the acknowledged hill. Restoring that snapshot and an intact log containing the committed write can recover both. Run a read for both identities, make one new write and record the elapsed recovery time. A reviewer can now compare observed data loss and time offline with the promises made before release. A successful deployment test on an empty database covers a different failure.

Try it

Run the browser experiment

Optional local lab

Complete the final assessment. Deliver a project that a second person can run, test, diagnose and restore using only its instructions.

Open the local exercise files

Check yourself

Which observation best closes the rollback drill?

Not quite. Starting the image alone does not verify service behavior. Re-read that part ↑

Right. A release gate connects a reproducible artifact to evidence that the service can serve real requests.

Why keep the exact identity of the image tested in staging?

Right. The release evidence refers to the tested artifact.

Not quite. The release evidence refers to the tested artifact. Re-read that part ↑

Which evidence exposes the limit of a noon-only backup?

Not quite. A healthy process can still be missing committed history. Re-read that part ↑

Right. A healthy process can still be missing committed history.

Sources

What you now know

A release gate connects a reproducible artifact to evidence that the service can serve real requests.