Event-Driven Architecture

This begins where a domain event leaves the process. The architecture skill owns the inside of a bounded context - returning events as values, one aggregate per transaction. This owns the wire: what happens once an event crosses a process or service boundary and someone you don't deploy with consumes it.

The move across that boundary is heavy and rarely the default. Reach for it when the coupling genuinely warrants it, not because events feel scalable.