create-domain-event

Domain events decouple domain logic from application services by defining data-only DomainEvent payloads in the domain layer and framework-backed handlers in the application layer. This propagates events across NestJS modules for asynchronous reactions.

The best way to structure domain events in a DDD NestJS project is to implement data-only DomainEvent definitions in the domain layer and nest their handlers in the application layer using the DomainEvent.base and OnEvent patterns.

You need domain events in a modular NestJS architecture when you want to connect a published domain event to reactive handlers across separate modules, enabling asynchronous reactions without tightly coupling domain logic to application services.

Yes, you can use the OnEvent pattern to handle domain events across different NestJS modules. The application layer handler reacts to the data-only domain event propagated from the domain layer, maintaining clean module boundaries.

Creating domain events using this approach requires no external dependencies. It implements data-only DomainEvent definitions and framework-backed handlers using the DomainEvent.base and OnEvent patterns natively within your NestJS project.

Domain events should be data-only definitions in the domain layer to carry payload without coupling to framework code. This ensures the domain logic remains clean while the application layer handles asynchronous reactions using NestJS decorators.