Hosting any web solution in your own process can be very useful in many scenarios. With the details in this chapter, you should be well on your way to do just that and have SignalR be your transport for communication.
Another aspect that often proves to be a source of debugging nightmare is scale out. State being kept in memory on one server is not available on the second, leading to weird scenarios and result. This is also vital when applying SignalR in a multiserver environment. There is no guarantee to what server the SignalR is connecting to. If the client needs to reconnect, then the scale out option is very vital to the story. With the different options described in this chapter, you should now be able to scale in an on-premise solution as well as in the cloud.
Note
You can find the entire sample code at https://github.com/dolittle/SignalR_Blueprints/tree/master/Source/Chapter10.
Although SignalR is very technical in nature and there are a lot of interesting things that it does...