Enterprise Architecture Patterns

This is a solid reference for building distributed systems at scale. It walks through the strategic and tactical sides of domain-driven design, including bounded contexts and context mapping patterns, then covers the operational patterns you need for microservices: event sourcing, CQRS, sagas for distributed transactions, API gateways, and service mesh. The code examples are practical, showing things like how to model entities versus value objects and how to avoid mixing domain models across bounded contexts. Use this when you're past the prototype phase and need to actually architect something that won't collapse under load or turn into a maintenance nightmare. It assumes you already know why you need these patterns, so if you're just exploring options, start with the CAP theorem and fallacies sections to ground yourself first.