NServiceBus Pub/Subscribe using SQLServer transport - can the subscriber scale out? -
Using the latest version of NServiceBus 4.4. I believe that
We are looking to implement NServiceBus and this section is using SQLServer as a transport. We want to pub / subscribe, which is fine, but how will it work with scaling customers?
I have made a point where I used to run the endpoint that received a SQL Server transport several times and when a message came in, the first instance of the moving receiver was received and processed, resulting in The other process was not processed, which is correct.
Subscribe to Architecture from Pub / Subscription to SQL Server Many examples of customer work are running and since we are using a common queue (SQL Server), it will sort itself and Many times the message will not process?
Comments
Post a Comment