Architecture Design
Principles & Patterns
A practical guide for solution architects: how to reason about trade-offs, draw better boundaries, and pick the right pattern for the problem in front of you.
Architecture Design Principles & Patterns
Most architecture guides tell you what the patterns are. Far fewer tell you when a pattern earns its place, and what it will cost you once it is in production. This one does the second thing.
Enter your email, confirm it, and the PDF downloads right away.
No spam, unsubscribe anytime.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
What is inside
Two parts. Part 1 is the grammar, Part 2 is the vocabulary. Every chapter in Part 2 ends with a when-to-use table, because a pattern catalog without selection guidance is just trivia.
Part 1
Design Principles
The reasoning tools that apply to every decision, regardless of technology.
- 1Thinking in Trade-offs
- 2Coupling and Cohesion
- 3Architecture Characteristics
- 4Decisions That Survive: ADRs and Fitness Functions
- 5Communicating Architecture
- 6Evolutionary Architecture and the Modular Monolith
- 7Measuring Success: DORA and Observability
Part 2
Pattern Families
The pattern groups a working architect reaches for most.
- 8Architecture Styles at a Glance
- 9Integration and Messaging Patterns
- 10Event-Driven Patterns
- 11Data Patterns
- 12Resilience Patterns
- 13Security Patterns
- 14Cloud and Deployment Patterns
- 15Patterns for AI Workloads
- 16Modernization Patterns
Appendix: Pattern Selection Sheet
Every when-to-use table collected in one place, so you can keep it next to the keyboard without reopening the guide.
Who it is for
Solution architects first: the people who have to connect business drivers to technical decisions, defend those decisions in front of stakeholders, and live with them for years. Software architects will find it equally usable, though the code stays light on purpose. Diagrams and trade-off tables carry the argument, because that is how architecture decisions are actually discussed in practice.
What it deliberately avoids
No silver bullets. Every pattern is presented together with the price you pay for it.
No invented case studies. Where an example comes from real project experience, it says so.
No chasing novelty. The patterns here have survived contact with production systems for years, which is what makes them safe foundations for your next decision.
Get the guide
Enter your email and we'll send you a confirmation link. Click it and the PDF downloads straight away. You also join the monthly newsletter on solution and software architecture. No spam, and you can unsubscribe at any time.
Get the PDF