Architecture Patterns Reference
A cheat sheet of software architecture patterns with when to use each, what it costs, and warning signs.
- Type
- Cheat sheet
- Access
- Free
- Format
- Published
- Nov 2, 2026
Hosted on Gumroad. It opens in a new tab.
What's inside#
- The forces that should drive an architecture choice
- Application structure patterns, from layered to microservices and serverless
- Integration patterns: gateways, BFF, service mesh, messaging, events and webhooks
- Data patterns: CQRS, event sourcing, outbox, change data capture and sagas
- Resilience patterns and safe ways to change a live system
- A decision guide and the anti-patterns to catch early
How to use it#
- Start from the problem and the forces on page 2, not from a favorite pattern.
- Use the "pays off when" and "costs" columns to compare options honestly.
- Check the anti-patterns list against your current system.
- Record the choice and its trade-offs in a design doc or decision record.
Limitations#
- Patterns are starting points, not prescriptions. Most real systems mix several.
- The comparison table is a simplification meant to start discussion.
- It doesn't replace deeper reading on any pattern you plan to adopt.
License
Free to use, share and adapt, including commercially, as long as you credit Letinix and link to this page. Licensed under CC BY 4.0.
Related reading
I Didn’t Rebuild My Portfolio to Look Better. I Rebuilt It to Be Found
A portfolio is often treated as a visual résumé: a polished landing page, a few project cards, and a contact link. I wanted mine to do more. This rebuild was about turning my portfolio into a durable professional platform. One that clearly
SaaS Gross Margin: Formula and Cost-of-Revenue Decisions
Learn the SaaS gross margin formula, work through an explicit example, and decide how hosting, support, engineering, and payment fees should be classified in your model.
Your Agent Passed the Eval. Its Retrieval Calls Still Tripled.
An AI agent can pass the task and still fail the engineering evaluation. That happens when a context-compression policy preserves the final outcome but changes how the agent gets there. The agent still completes the benchmark. It also
Related tools
More resources
Technical Design Doc Template
A free template for proposing a system change, showing the evidence behind it, and getting a clear decision from reviewers.
Tech Lead Toolkit
Five printable worksheets for tech leads: delegation levels, stakeholder map, decision brief, pre-mortem and one-on-one template.
System Design Cheat Sheet
A dense reference to system design concepts, estimation numbers, building blocks and trade-offs.