Data distribution

Component: NServiceBus
NuGet Package NServiceBus (7.x)
Asynchronous messaging is not an optimal solution for data distribution scenarios. It is usually better to use a dedicated data distribution technology for that purpose, such as a distributed cache or distributed configuration service.

The NServiceBus Publish-Subscribe implementation is designed to deliver events to a single physical instance of a logical subscriber. In order to distribute data, it may be necessary to deliver events to all physical instances of a logical subscriber. While it is usually better to use a dedicated data distribution technology for that purpose, such as a distributed caching solution, NServiceBus can also be used to distribute data.

A logical subscriber is defined by its endpoint name. In a data distribution scenario, each physical subscriber has to act as if it were a unique logical subscriber. That is, it has to be given a unique endpoint name. Usually that name consists of the logical name e.g. WebFrontend and a suffix which can be either read from a configuration file or obtained from the environment (e.g. an Azure role instance ID). This pattern is described in more detail in the data distribution sample.


Last modified