new-event

To wire a new domain event across microservices, you provide the EventName, PublisherAggregate, and ConsumerAggregate to generate the event class, subscription, handler, and polling wiring artifacts for the publisher and consumer services.

Event subscription between publisher and consumer aggregates works by using anchor-based subscriptions where the subscribedAggregateId aligns with the anchor IDs, ensuring domain events are delivered correctly across the microservices-simulator.

You need three arguments to generate domain event classes and polling wiring: the EventName, the PublisherAggregate, and the ConsumerAggregate. These inputs produce the wired event class, subscription, and handler artifacts.

Yes, you can use this to propagate state changes across aggregates in a microservices-simulator. It generates the necessary event class, subscription, handler, and polling wiring to connect publisher and consumer aggregates within the quizzes module.

The best way to add an event handler and subscription for a new domain event is to generate them simultaneously with the event class and polling wiring by specifying the EventName, PublisherAggregate, and ConsumerAggregate for the quizzes module.

The subscribedAggregateId must align with anchor IDs during event wiring to ensure the subscription correctly routes the domain event from the publisher aggregate to the consumer aggregate within the microservices-simulator.