SignalR 1.1 beta

We released SignalR 1.1 yesterday with a bunch of performance improvements and new features (detailed in the release notes). Among these new features, were improvements to the .NET client including the ability to set custom headers, client certificates and a custom JSON serializer. We also fixed a long standing issue people were experiencing in IE7 and IE8 with the loading bar showing up forever in the browser. However, most of this release focused on rewriting SignalR’s scaling out story from the ground up.

Scaling out

The previous releases of SignalR’s scale out implementation did not handle a lot of scenarios when it came to scaling it across web servers. We took a step back and redesigned the core scale out architecture and backplanes for SQL Server, Azure Service Bus and Redis.

There are now 3 new packages on NuGet that you can choose from when scaling out SignalR:

  1. SQL Server
  2. Azure Service Bus
  3. Redis

These backplanes share a common base class (ScaleoutMessageBus) that contains the core logic allowing SignalR to work across a webfarm.

Using Scale out

Registering a backplane hasn’t changed much from the previous versions but there are some new features to be aware of.

ALL backplanes

Scale out backplanes have 2 modes controlled by a single flag RetryOnError. Users can create a configuration object for their backplane and specify which mode they want to use. This flag determines if SignalR should start buffering messages when the scale out backplane encounters errors; by default this flag is false. Here is an example:

 

 

In the above scenario, if the Redis service went offline, with RetryOnError = false the call to send a message to all clients would throw synchronously. If RetryOnError was true, the OnError callback would be raised the call would be queued until Redis came back online. This queue does have a limit and when it is full it will also fail.

 

SQL SERVER

  • The SQL backplane requires that you create the database before hand.
  • The SQL scale out backplane works with or without service broker turned on.
  • Performance is usually better with service broker on since this enables query notifications to work.

Once the database is set up, you can enable SQL like this:

It’s all you need to get running with SQL server.

 

SERVICE BUS

The new service bus scale out backplane only works with the Windows Azure service. The wiki has been updated with new steps that show how to setup service bus on Windows Azure.

Windows Azure Websites is also supported.

TRACING

If you are encountering problems with scale out and want to troubleshoot what’s going on, you can turn on tracing with this xml snippet in your config file:

 

 

The purpose of this beta release is to get feedback, so do give it a try and let us know what you think. As always, file issues on github, and questions on stackoverflow, jabbr or the SignalR forum.

Published Thursday, April 11, 2013 10:54 PM by davidfowl

Comments

# re: SignalR 1.1 beta

Friday, April 12, 2013 7:38 PM by Chris Kirby

Just from a configuration and diagnostics standpoint, this is a huge improvement. I'll be trying this on service bus right away with one of my multi instance azure websites. Thanks!

# re: SignalR 1.1 beta

Sunday, April 14, 2013 10:19 AM by Maya

where can I find the SQL Schema definition needed for SQL Server based scale-out implementation?

Thanks,

Maya