The SignalR team provides a third backplane option, based on Microsoft SQL Server. This one could be a good fit if both Windows Azure and Redis are not an option for you. It has good resilience characteristics, although it's not the best option in terms of performance.
In this recipe, we'll assume you have a SQL Server instance available, and we'll see how to plug the SQL Server backplane into a simple application inspired by the previous scale-out recipes.
As we did previously, we'll reuse the code we wrote in the recipe about the Windows Azure Service Bus backplane, and we'll just show what's to be different when we add the SQL Server backplane. We'll perform our demonstration using a new empty web application named Recipe40.
In order to correctly support the backplane, we need to perform the following actions:
We need to create an empty database. It does not need to have any special name, and the necessary tables will be created by the backplane...