Search code examples
.netnservicebuspublish-subscribe

How to scale out a NServiceBus publisher


I know there should not be multiple publishers publishing the same event. But how should I scale out a subscriber that publishes an event after it processed the event it is subscribed to? Scaling this out will result in multiple publishers publishing the same event.

When searching on google I get conflicting answers. One says I should use send instead of publish and another source says just to use a shared subscription storage.

I would probably go with a shared subscription storage but I'm not sure if this will work properly.


Solution

  • If I'm reading this correctly I would leverage the Distributor to scale the Subscribers out. If you are using 3.0, this would include adding another node and a small amount of config. If you are using 2.x, this involves a bit more setup including another endpoint. There are some visuals on the site.