domain-events

An event bus enables pub/sub communication by allowing modules to register as listeners for typed domain events while domain services emit events with structured payloads, achieving decoupled event-driven architecture.

Decouple services by registering modules as event pushers on a central event bus, enabling domain services to emit typed events like 'booking:created' that other modules subscribe to without direct dependencies.

Yes, you can test event-driven logic in isolation by calling the clearEventPushers utility, which clears event subscriptions to ensure subscribers are not triggered during testing.

TypeScript event-driven architecture supports typed payloads for domain events, providing a type-safe system where domain services publish structured data that subscribers receive with full type checking.

The best way to structure event subscriptions is through a central event bus where modules register as listeners for specific event types, allowing domain services to emit structured events that automatically trigger the correct subscribers.

A central event bus for domain events should not be used when modules require synchronous, tightly coupled execution or when the testing overhead of managing and clearing event subscriptions outweighs the benefits of decoupling.