CODEWITHSUNDEEP
publish-subscribemasstransit
Itay Angel
Itay Angel

Reputation: 25

MassTransit Ensure Queues Created before Publishing Messages

We have multiple services and use the publish/subscribe pattern for sending events from service A to be handled by other services (B & C). The goal is to allow multiple queues to receive messages from a Producer by matching the binding key / topic.

This works fine if services B & C start first. In that case, the Subscribe method creates the Exchanges and Queues to receive the messages when published. However, if service A starts first, then the published messages are lost as the receiving queues are not created.

Looking for the Best Practice way to ensure the queues are created before publish. The producer does not have knowledge of the consumers, and there may be more consumers over time for a given message type, so we can't have the producer code take responsibility for queue creation.

Our current implementation is using RabbitMQ on the backplane, but we want to migrate over time to SQS and Azure Service Bus, so we need this to be Message Broker agnostic

Upvotes: 1

Views: 1761

Answers (1)

Chris Patterson
Chris Patterson

Reputation: 33268

The simple answer, start your consumer services before you start your publishers.

Alternatively, you could use the DeployTopologyOnly flag with a custom build or command-line to deploy the queue/exchanges/bindings without actually starting the consumers, but it will still be the consumer service with all of its configuration.

Upvotes: 2

Related Questions