One-line summary of what this pattern does.
Two or three sentences explaining the concept in plain language.
- Bullet points describing the situations where this pattern applies.
- Keep them concrete (for example "read-heavy workloads with a high cache hit ratio").
A short explanation of the mechanism. A small ASCII or Mermaid diagram helps:
[client] --> [component] --> [data store]
| Pro | Con |
|---|---|
| Benefit | Cost or risk |
| Benefit | Cost or risk |
- Variation one and when you would pick it.
- Variation two and when you would pick it.
A sentence or two on the signal interviewers look for, and the follow-up questions to expect.
Link to the relevant lesson in System Design Patterns or the main course.