pattern-mediator

To decouple tightly coupled components, route their interactions through a centralized mediator interface. Participants broadcast events via a notify method instead of invoking peers directly, centralizing coordination logic and removing tangled imports.

In event bus and CQRS architectures, a mediator pattern centralizes routing logic to orchestrate command handlers and event workflows. It drives workflows by routing interactions through a single interface, ensuring services coordinate without direct dependencies.

Coordinate UI components and services by declaring a mediator contract with a notify method. Every participant broadcasts events through this bridge instead of referencing peers directly, avoiding dependency hell and keeping coordination logic centralized.

Yes, the mediator pattern works for orchestrating command handlers in a CQRS setup. It centralizes command routing by having components interact solely through a mediator interface, decoupling the command sender from its specific handler implementations.

Avoid using a centralized mediator for component messaging when components have very few interactions or when routing logic becomes a monolithic bottleneck. If objects do not risk creating tangled imports, direct communication may be simpler than centralizing coordination.