Geek asks and answers

Signal scaling using the Windows Azure service bus

I have an application that uses SignalR to connect users on my site to things like chat. If I only open my site to the public for the first time, I would suggest that I need only one copy for the first few months of use (if demand does not require another copy). Can I run my signalR hub in the same instance without using the Windows Azure service bus and then move it to the service bus when I use two or more instances?

Also one quick question on the Windows Azure Service Bus website:

The Service Bus enables up to 100 concurrent connections to an entity.

Does this mean only 100 concurrent users connected to the service bus? or 100 simultaneous connections to instances? I could see how only 100 concurrent users can be very limited in terms of large-scale websites, so I guess this means cases? A little confused about how the architecture will work when you switch to the service bus with concurrently connected users.

+5
source share
1 answer

Your users will connect to your instances, and your instances will connect to the service bus. I do not say 1 connection = 1 connection (I do not know how SignalR.WindowsAzureServiceBus works inside), but you will not reach the limits when starting multiple instances.

SignalR.WindowsAzureServiceBus , , SignalR .

"" SignalR Windows Azure SB (. : http://www.asp.net/signalr/overview/performance/scaleout-with-windows-azure-service-bus). , SLA Windows Azure , 2 .

+9

More articles:


All Articles