Distributed System Patterns
Distributed systems trade local simplicity for independent ownership, scale, and change. This part makes those trade-offs visible through service boundaries, events, messages, workflows, contracts, and failure behavior.
What You Will Learn
Decide when service decomposition is justified.
Separate event notification from reliable work and streaming.
Design retries, idempotency, ordering, replay, and dead-letter handling.
Choose orchestration, choreography, messaging, and integration patterns deliberately.
Chapters
Microservices Architecture — connect service and data boundaries to team ownership and failure isolation.
Event-Driven Architecture — design event sources, routing, processing, contracts, and operations.
Workflow, Messaging, and Enterprise Integration Patterns — coordinate reliable work across systems and organizational boundaries.
How the Chapters Connect
Microservices establish independently owned boundaries. Event-driven architecture loosens communication between them. Workflow and messaging patterns then provide explicit coordination when work must be reliable, observable, and recoverable.