Grokking Microservices Design Patterns
The named patterns that make service architectures survivable, including API gateway, circuit breaker, bulkhead, sidecar, saga, CQRS and event sourcing. Each one exists because someone lost a weekend to the problem it solves.
Course
System Design
Design Gurus
3 weeks
Advanced
Subscription
What it is
A pattern catalogue for service architectures. Decomposition patterns, integration patterns such as API gateway and backend for frontend, resilience patterns such as circuit breaker, retry with backoff and bulkhead, data patterns such as saga, CQRS and event sourcing, and the cross cutting concerns of configuration, discovery and tracing.
Why they are worth naming
These patterns are not academic. Every one of them is a fix for a specific production failure: a slow dependency taking down a healthy service, a retry storm amplifying an outage, a transaction that cannot span two databases. Knowing the name gives you a shared vocabulary with the interviewer and with your future colleagues.
How to use it
For each resilience pattern, write down the outage it prevents in one sentence. If you cannot, you have learned the name and not the pattern.
Best for: engineers designing or operating service architectures, and senior interview candidates.
Ready to start?
Opens on Design Gurus in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
Follow along
New writing, resources and project ideas land here first.