Stay Practiced.
Local toolsSite guideSettings
Curriculum

Backend reliability engineering

Design service boundaries, validation, persistence, concurrency, queues, deadlines, observability and recovery across complete incidents.

20 units · Web, Plus, Pro · 20 programming subjects + 2 security tracks

Branches show this unit’s authored theory, coding and assessment work.

Select a node. Drag the background to pan.100%

Unit 1 / 20

Keep a crawler from creating reservations

Reject an unsafe state-changing use of a safe HTTP method before accepting any reservation effect.

0 prerequisite skills · Reading, guided completion and independent success remain separate evidence.

Open this unit

The course, in order

Open a unit in the map to inspect its activities. Reading, guided completion, independent work and review remain distinct evidence.

  1. Keep a crawler from creating reservations

    Reject an unsafe state-changing use of a safe HTTP method before accepting any reservation effect.

    Open this unit
  2. Reject an unsupported export representation early

    Reject an unsupported representation before acquiring or constructing an export body.

    Open this unit
  3. Keep a supplied filter operator outside the query language

    Translate only allowlisted filter operators so caller values cannot extend the query language.

    Open this unit
  4. Reject an unrelated site changing a cookie-authenticated record

    Validate the intended request origin before a cookie-authenticated mutation, rejecting ambiguous or unrelated origins.

    Open this unit
  5. Keep a membership from outliving its missing owner

    Keep a stored membership tied to an existing owner through the actual relationship constraint.

    Open this unit
  6. Prepare a remote quote without holding a scarce transaction

    Acquire a remote quote before opening the scarce local transaction that commits its checked result.

    Open this unit
  7. Refuse a page cursor borrowed from another search

    Bind a continuation cursor to the original search scope rather than accepting a cursor borrowed from another query.

    Open this unit
  8. Stop a two-account transfer from forming a lock cycle

    Acquire account locks in one shared ordering so two opposite transfers cannot form a lock cycle.

    Open this unit
  9. Keep tenant scope on storage and cached results

    Include authenticated tenant scope in both storage lookup and cache identity.

    Open this unit
  10. Decide a rollout from bad events in the declared window

    Evaluate the declared bad-event budget over the correct eligible window instead of an unrelated aggregate.

    Open this unit
  11. Publish one validated configuration revision to every request

    Validate a complete configuration before atomically publishing one revision to every request owner.

    Open this unit
  12. Choose the declared overflow policy without growing memory

    Apply the declared bounded-queue overflow policy without silently accepting an unbounded memory obligation.

    Open this unit
  13. Spread a retry wave while respecting its cap

    Spread retry attempts under the stated jitter and cap policy without exceeding the permitted delay.

    Open this unit
  14. Locate the slow minority hidden by an acceptable median

    Locate the slow minority in the supplied latency distribution instead of accepting a favorable median.

    Open this unit
  15. Drain accepted work before releasing service resources

    Withdraw admission before draining accepted work and release service resources only after the owned drain settles.

    Open this unit
  16. Keep an unvalidated upload outside the public object namespace

    Hold unvalidated uploaded bytes outside the public namespace and publish only a checked accepted object.

    Open this unit
  17. Fence an old rollout coordinator after leadership changes

    Fence rollout publication to the current coordinator token so a replaced leader cannot overwrite accepted state.

    Open this unit
  18. Report partial batch acceptance without pretending atomicity

    Report each independently durable batch result without claiming the whole batch committed atomically.

    Open this unit
  19. Find a cross-row anomaly behind repeatable reads

    Recognize a cross-row write anomaly that repeatable individual reads alone do not prevent.

    Open this unit
  20. Find the failed owner behind a chain of downstream symptoms

    Find the first failed fact owner in a dependency chain before treating downstream symptoms as independent causes.

    Open this unit
TheoryHands-on codingEvidence / reviewTechnical wikiMembership access