2.3.1 Event-Driven Architecture
A service writes an event to a bus. Others subscribe and update their own data.
Why it matters
You avoid a web of synchronous calls. New subscribers can appear without changing the publisher.
How it is used
Events are past tense and immutable. Include enough data (or a pointer). Design for at-least-once delivery: consumers must be idempotent.