Light atlas / architecture patterns
Navigate system design by constraint, not by buzzword.
A cartographic reference for 100 patterns engineers reach for when systems stretch, fail, drift, queue, split, cache, coordinate, migrate, secure, and recover.
Start with the force acting on the system: latency, growth, failure, coordination, migration, security, or visibility.
Name the pattern, explain the mechanism, then own the trade-off.
Do not decorate architecture. Every pattern should absorb a specific pressure.
Pattern map
33 pressure territories. One hundred 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
Consistency / Messaging
3 patterns
Consistency / Workflow
1 patterns
Data / Query
2 patterns
Consistency / Storage
3 patterns
Coordination
4 patterns
Execution
3 patterns
Communication
1 patterns
Latency
1 patterns
Caching / Latency
2 patterns
Traffic Control
4 patterns
Reliability
3 patterns
Reliability / Caching
1 patterns
Availability
3 patterns
Availability / Scale
1 patterns
Availability / Multi-Tenant
1 patterns
Migration
3 patterns
Migration / Testing
1 patterns
Release
3 patterns
Data Evolution
3 patterns
Data Lifecycle
2 patterns
Security / Operations
2 patterns
Security
2 patterns
Architecture
1 patterns