{"id":98143,"date":"2019-08-09T06:41:06","date_gmt":"2019-08-09T06:41:06","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/aspnet\/?p=22298"},"modified":"2019-08-09T06:41:06","modified_gmt":"2019-08-09T06:41:06","slug":"azure-signalr-service-now-supports-event-grid","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2019\/08\/09\/azure-signalr-service-now-supports-event-grid\/","title":{"rendered":"Azure SignalR Service now supports Event Grid!"},"content":{"rendered":"
\n
\n
\"Avatar\"<\/p>\n

Ken<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n

August 8th, 2019<\/p>\n<\/p><\/div>\n

<\/p>\n

Since we GA\u2019ed Azure SignalR Service in last September, serverless has become a very popular use case in Azure SignalR Service and is used by many customers. Unlike the traditional SignalR application which requires a server to host the hub, in serverless scenario no server is needed, instead you can directly send messages to clients through REST APIs or our management SDK which can easily be used in serverless code like Azure Functions.<\/p>\n

Though there is a huge benefit which saves you the cost of maintaining the app server, the feature set in serverless scenario is limited. Since there is no real hub, it\u2019s not possible to respond to client activities like client invocations or connection events. Without client events serverless use cases will be limited and we hear a lot of customers asking about this support. Today we\u2019re excited to announce a new feature that enables Azure SignalR Service to publish client events to Azure Event Grid so that you can subscribe and respond to them.<\/p>\n

How does it work?<\/h2>\n

Let\u2019s first revisit how serverless scenario in Azure SignalR Service works.<\/p>\n

    \n
  1. \n

    In serverless scenario, even you don\u2019t have an app server, you still need to have a negotiate API so SignalR client can do the negotiation to get the url to SignalR service and a corresponding access token. Usually this can be done using an Azure Function.<\/p>\n<\/li>\n

  2. \n

    Client will then use the url and access token to connect to SignalR service.<\/p>\n<\/li>\n

  3. \n

    After clients are connected, you can send message to clients using REST APIs<\/a> or service management SDK<\/a>. If you are using Azure Functions, our SignalR Service binding<\/a> does the work for you so you only need to return the messages as an output binding.<\/p>\n<\/li>\n<\/ol>\n

    This flow is illustrated as step 1-3 in the diagram below:<\/p>\n

    \"Serverless<\/p>\n

    What\u2019s missing here is that there is no equivalent of OnConnected()<\/code> and OnDisconnected()<\/code> in serverless APIs so there is no way for the Azure function to know whether a client is connected or disconnected.<\/p>\n

    Now with Event Grid you\u2019ll be able to get such events through an Event Grid subscription (as step 4 and 5 in the above diagram):<\/p>\n

      \n
    1. \n

      When a client is connected\/disconnected to SignalR service, service will publish this event to Event Grid.<\/p>\n<\/li>\n

    2. \n

      In Azure function you can have an Event Grid trigger and subscribe to such events, then Event Grid will send those events to the function (through a webhook).<\/p>\n<\/li>\n<\/ol>\n

      How to use it?<\/h2>\n

      It\u2019s very simple to make your serverless application subscribe to SignalR connection events. Let\u2019s use Azure function as an example.<\/p>\n

        \n
      1. \n

        First you need to make sure your SignalR Service instance is in serverless mode. (Create a SignalR Service instance<\/a> if you haven\u2019t done so.)<\/p>\n

        \"Enable<\/p>\n<\/li>\n

      2. \n

        Create an Event Grid trigger in your function app.<\/p>\n

        \"Create<\/p>\n<\/li>\n

      3. \n

        In the Event Grid trigger, add an Event Grid subscription.<\/p>\n

        \"Add<\/p>\n

        Then select your SignalR Service instance.<\/p>\n

        \"Select<\/p>\n<\/li>\n<\/ol>\n

        Now you\u2019re all set! Your function app is now able to get connection events from SignalR Service.<\/p>\n

        To test it, you just need to open a SignalR connection to the service. You can use the SignalR client in our sample repo, which contains a simple negotiate API implementation.<\/p>\n

          \n
        1. \n

          Clone AzureSignalR-samples<\/a> repo.<\/p>\n<\/li>\n

        2. \n

          Start the sample negotiation server.<\/p>\n

          cd samples\\Management\\NegotiationServer\nset Azure__SignalR__ConnectionString=<connection_string>\ndotnet run\n<\/code><\/pre>\n<\/li>\n
        3. \n
          Run SignalR client.<\/p>\n
          cd samples\\Management\\SignalRClient\ndotnet run\n<\/code><\/pre>\n
          Open the function logs in Azure portal and you\u2019ll see a connected event is sent to the function:<\/p>\n
          \"Azure<\/p>\n
          If you stop the client you\u2019ll also see a disconnected event is received.<\/p>\n<\/li>\n<\/ol>\n
          Try it now!<\/h2>\n
          This feature is now in public preview so feel free to try it out and let us know your feedback by filing issues on Github<\/a>.<\/p>\n
          For more information about how to use Event Grid with SignalR Service, you can read this article<\/a> or try this sample<\/a>.<\/p>\n
          \n
          \"Avatar\"<\/div>\n
          \n
          Ken Chen<\/a><\/h5>\n
          Principal Software Engineering Manager<\/p>\n
          Follow Ken<\/strong>   <\/i><\/a><\/a><\/p>\n<\/p><\/div>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
          Ken August 8th, 2019 Since we GA\u2019ed Azure SignalR Service in last September, serverless has become a very popular use case in Azure SignalR Service and is used by many customers. Unlike the traditional SignalR application which requires a server to host the hub, in serverless scenario no server is needed, instead you can directly […]<\/p>\n","protected":false},"author":2,"featured_media":98144,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[66],"tags":[54,105,355],"class_list":["post-98143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-webdev","tag-azure","tag-serverless","tag-signalr"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/98143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=98143"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/98143\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/98144"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=98143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=98143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=98143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}