As a product owner, I want the whole backend organized where MassTransit is implemented. Messages and Consumers should be organized per context.
Events are multicast for multiple consumers, commands for single consumer. So consumer has their own input queue which messages are being routed via exchanges.
Each message type, MassTransit creates (by default ) a fanout exchange based on the message type, fanout exchange and queue for each consumer.
Three dependency like:
EventTypeExchange > ConsumerExchange > ConsumerQueue
As a product owner, I want the whole backend organized where MassTransit is implemented. Messages and Consumers should be organized per context.
Events are multicast for multiple consumers, commands for single consumer. So consumer has their own input queue which messages are being routed via exchanges.
Each message type, MassTransit creates (by default ) a fanout exchange based on the message type, fanout exchange and queue for each consumer.
Three dependency like: EventTypeExchange > ConsumerExchange > ConsumerQueue