4.1. Integration & Messaging Patterns

💡 First Principle: Loosely coupled services communicate through messages, not direct calls — this makes each service independently deployable, scalable, and fault-tolerant.

What happens when Service A calls Service B directly, and Service B goes down? Service A fails too — a cascading failure. SQS, SNS, EventBridge, and Step Functions break this dependency chain. Without them, distributed applications become fragile monoliths connected by HTTP calls. For example, consider an order processing system: when the payment service calls the inventory service directly, a 2-second inventory delay slows down every checkout.

Think of it like the difference between calling someone on the phone (synchronous — both parties must be available) versus leaving a voicemail (asynchronous — the message waits until they're ready). SQS is the voicemail box, SNS is a broadcast announcement, EventBridge is a smart mailroom that routes by content, and Step Functions is a project manager coordinating multi-step work.