Service Communication Patterns

Communication style determines whether a service boundary behaves as a clean separation or a constant coordination problem. Chapter 7 shifts the discussion from structure alone to interaction: when synchronous calls are justified, where asynchronous messaging helps, how contracts should be shaped, and what chatty behavior reveals about a weak boundary.

Read the lessons in order. The first covers synchronous calls and their hidden costs. The second explains asynchronous messaging and event-driven interaction without pretending the complexity disappears. The third focuses on API contracts, consumer pressure, and how surface area grows in unhealthy ways. The fourth turns chatty communication into a design smell that can trigger contract reshaping or even boundary merger.

If a service map looks clean but ordinary workflows still require too many small calls, Chapter 7 is the place to challenge the interaction model rather than blaming the network alone.

In this section

• Synchronous Calls and Their Hidden Costs
  A practical lesson on when synchronous service calls are appropriate, what kinds of coupling they introduce, and why long call chains often signal weak boundaries.
• Asynchronous Messaging and Event-Driven Interaction
  A practical lesson on using events, queues, and pub-sub to reduce temporal coupling while managing idempotency, retries, ordering, and observability.
• API Contracts, Consumer Needs, and Surface Area
  A practical lesson on shaping service APIs around stable business interactions instead of leaking internal implementation details under consumer pressure.
• Chatty Services and Coordination Smells
  A practical lesson on recognizing chatty service behavior as a sign of weak boundaries, overly fine-grained contracts, or workflows that still want more cohesion.