Capstone: a resilient service
P38.services.02 · Audience: guest, it-ml, language-pro · Prerequisites: APIs & service design, Monolith vs microservices & distributed basics
A real service never gets to practise one skill at a time: the request that needs a clean seam to test against is the same request that must survive a retry and a flaky dependency. That is why this capstone asks for all of P38 at once. You'll build a small order service that is well-architected (its store arrives as an injected port), correct under retries (idempotent by key), and resilient (it retries a flaky dependency with backoff). It's the kind of service you'd package (P35), gate in CI (P36), and make observable (P37) — the whole pillar converging on one artefact.
ⓘ Concept: Architected + idempotent + resilient
Why it matters — Real services need all three at once: a clean seam to test against, exactly-once effects under retries, and survival of transient failures — this is where they combine.
Ask the mentor about this module
Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.
Keeping your files on this device
Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.
🎓 Practice ladder
1 graded rung · ~40 minBuild a resilient, idempotent order service over an injected store — graded by hidden tests and a design rubric.
Capstone — a resilient service (project)
Loading exercise…
That's the production discipline in miniature — architected, correct, and resilient. The remaining track zooms out to where these services live: distributed systems.
My notes on this module
Loading your notes...