Light atlas / architecture patterns
Navigate system design by constraint, not by buzzword.
A cartographic reference for the 50 patterns engineers reach for when systems stretch, fail, drift, queue, split, cache, and recover.
How to use it
Start with the force acting on the system: latency, growth, failure, coordination, or visibility.
What to say
Name the pattern, explain the mechanism, then own the trade-off.
What to avoid
Do not decorate architecture. Every pattern should absorb a specific pressure.
Pattern map
Ten pressure territories. Fifty pattern paths.
Data Storage Patterns
6 patterns
Caching Patterns
5 patterns
Communication Patterns
7 patterns
Reliability Patterns
7 patterns
Scaling Patterns
5 patterns
Data Processing Patterns
4 patterns
API Design Patterns
5 patterns
Infrastructure Patterns
4 patterns
Consistency Patterns
4 patterns
Observability and Operations Patterns
3 patterns