Skip to content

DevCDR with Azure SignalR Service

Jump to bottom
Roger Zander edited this page Oct 12, 2019 · 5 revisions

DevCDR can use Azure SignalR Service instead of hosting an own SignalR Hub (https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-overview). This allows to scale out and increase the max. amount of concurrent devices in DevCDR. azuresignalr

Note: An Azure SignalR Service Unit (Includes 1'000 concurrent connections per unit and 1'000'000 messages per unit/day) costs ~50$/Month. A max of 100 units can be configured.

Setup

NEW: Since Version 2.0.0.29, you can use the "normal" Branch ServerCore21 together with Azure SignalR Service. There is no need to install a special version. Just follow the configuration in Configure

You have to deploy a customized version from Branch ServerCore_AzureSignalR.

Just open: https://github.com/rzander/DevCDR/tree/ServerCore_AzureSignalR and click on

Configure

In the Azure App Service, go to Configuration and update the Azure:SignalR:ConnectionString with your Connection-String for your Azure SignalR Service:

setting

Clone this wiki locally