Account

Capstone: a resilient service

P38.services.02 · Audience: guest, it-ml, language-pro · Prerequisites: APIs & service design, Monolith vs microservices & distributed basics

Real LLM grading for this pageLLM grading (this page):

The pillar in one exercise. You'll build a small order service that is well-architected (depends on an injected port), correct under retries (idempotent by key), and resilient (retries a flaky dependency with backoff) — the three ideas of P38 in one place. It's the kind of service you'd package (P35), gate in CI (P36), and make observable (P37): the production discipline, end to end.

Step 1 / 2 — Three ideas, one service
ⓘ Concept: Architected + idempotent + resilient
The service depends on a persistence port (injected, not constructed) — that's the architecture. It's idempotent by key, so a retried request creates one order. And it retries the store's transient failures with backoff, surfacing a permanent failure rather than dropping it. Each is a P38 idea; together they're a service you can trust.

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.

Ctrl/Cmd + Enter to send

🎓 Practice ladder

1 graded rung · ~40 min

Build 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.

Where next?

Continue

Monolith vs microservices & distributed basics →

Distribution & Distributed Basics · P38

Go up a level