CommunicationPatterns
How services/components talk to each other — transport and interaction style, not the API contract shape (see APIDesign).
Why we need this / what value this brings
Choosing the wrong interaction style (sync where async would do, or vice versa) creates either unnecessary latency coupling or unnecessary complexity.
When to use this
Decide per-interaction, at the point you're designing how two components will talk.
How to use or implement this
Default to synchronous request/response until a specific pain point (latency coupling, need for retry/replay) justifies async.
Subtopics
Empty folder — drop notes, links, and findings here as you research.