Announcing Serverless Support for Socket.IO in Azure Web PubSub service
Socket.IO Serverless Mode in Azure Web PubSub service is now available. This new mode eliminates the need for developers to maintain persistent connections on their application servers, offering a more streamlined and scalable approach. In addition to the existing default mode, developers can now deploy Socket.IO applications in a serverless environment using Azure FunctionsAnnouncing MQTT Support in Azure Web PubSub Service (public preview)
We're excited to announce the long-requestedrelease of MQTT support in Azure Web PubSub service, now available in preview! This added capability allows developers to leverage the lightweight and widely used MQTT protocol for messaging, making it easier to connect and communicate with devices that have constrained resources.Socket.IO support on Azure
Socket.IOis a wildly popular open-source library for client-server real-time communication. While Socket.IO user love the intuitive APIs, scaling out a Socket.IO app is not something developers are particularly fond of.I am happy to share that with the input from the open-source community we brought support forSocket.IOon Azure. With this support,Azure hosts and manages client connections so that Socket.IO developers don't have to. For developers who are familiar with Socket.IO, it means you dont need to develop, deploy or maintainer an "adapter" component. Getting a Socket.IO app running locally to Azure takes only a few lines of code.With geo-replica, Web PubSub resources are fault tolerant and can communicate across regions
Azure Web Pub announces the GA status of the geo-replia feature. Having a failover strategy in place is a must for enterprise-grade applications. What used to take much effort and time can now be configured quicky with a few clicks. Plus, end users from geographically distant locations can benefit from low latency they expect from a real-time system.Native support for Socket.IO on Azure, scalability issue no more
This article talks about a popular open-source library called “Socket.IO”. It’s often used to build real-time web applications, like multi-player games and co-editing, co-creation applications. It explores the relationship between WebSocket API, Socket.IO library and an Azure service. WebSocket API – provides the transport-level plumbing of bi-directional communication between clients and server. Socket.IO library – builds on top of WebSocket API and provides application-level features that are common when developing real-time web apps. Azure Web PubSub for Socket.IO – a feature from an Azure service that provides the infrastructure for massive scalability of Socket.IOapps.Azure Web PubSub for Socket.IO is now generally available
TL;DR Socket.IO library is natively supported on Azure. Since we public previewed this feature, we received positive feedback from users. Now we are happy to share that Web PubSub for Socket.IO is generally available, which means that Azure customers can expect stable APIs, SLAs customer support and it’s suitable for use in production. Follow this quickstarts guide to try out the feature. Check out the repo of a collaborative whiteboard app that showcases the use of Socket.IO APIs and how Azure handles scalabilitychallenges.
Communicate Realtime on Azure with Web PubSub
Azure Web PubSub is a PaaS Service on Azure to send real-time messages and notifications between Web and Mobile applications using WebSockets. This uses a Publish/Subscribe model and allows sending notifications, updates, messages between various connected entities.Expand your application with real-time messaging API capability with Web PubSub and API Management
Businesses everywhere are looking to extend their operations as a digital platform, creating new channels, finding new customers, and driving deeper engagement with existing ones. Now, with the API Management (APIM)and Web PubSub service (AWPS), you are able to expand the real-time messaging capability of your application with a consistent and modern API gateway. Build apps faster and deliver immediate value to your customers through API-first approaches. Transform your legacy services into modern REST-based APIs or WebSocket APIs. Consistent experience to manage APIs (REST and WebSocket) across clouds and on-premises. Let’s go through the key steps together and learn how to implementthisreference solution: Createthe Azure Web PubSub Service Create the Azure API Management service and configure the WebSocket rules Test it with a live demo Setup Web PubSub Follow the steps to create your Web PubSub service which we refer to as AWPS1 in the following sections. When created, go to the Keys tab for the resource from theAzure portal, and you can see the hostname and connection strings of your resource.There is also a Client URL Generator tool in the portal that it can generate some temporarily valid URLs for your WebSocket clients to connect to. Let's use this tool to generate an URL for our demo with a hub called demoHub. This tool is for quick test purposes, we also provide APIs in various languages to generate the URL for production usage, for example, WebPubSubServiceClient.GetClientAccessUri Method for .NET. Copy the generated Client Access URL for later use. You can see that this Client Access URLcontains: the hostname of the Web PubSub service xxx.webpubsub.azure.com with wss scheme, and the path containing the hub name /client/hubs/demoHub, and a query parameter access_token which is the JWT token that the Web PubSub service uses to validate and authenticate the WebSocket clients. Setup API Management Follow the steps to create your API Management service which we refer to as APIM1 in the following sections. When created, go to the APIs tab for the resourcefrom theAzure portal, click Add API and choose WebSocket Create with the following parameters: WebSocket URL:wss://<your_webpubsub_name>.webpubsub.azure.com/client/hubs/demoHub Replace <your_webpubsub_name> with the name of your AWPS1 API URL suffix:client/hubs/demoHub Now you are all set, select the API and use the Test tab to test the connection. Remember the access_token queryparameter we get from the AWPS1 Client Access URL? Paste it here as the access_token query parameter, and Connect. You can now see in theoutputConnected. Try samples Let's update this simple publish and subscribe message sampleto use APIM1, the only thing to change is to let the WebSocket subscriber connect to APIM1instead. After the subscriber getsthe full URL to connect to AWPS1, let's update the URL to connect to APIM,and don't forget to append the subscription-key query parameter if your APIM settings enabled it, for example, in C#, update the code as below: static async Task Main(string[] args) { // ... var serviceClient = new WebPubSubServiceClient(connectionString, hub); var url = serviceClient.GetClientAccessUri(); // Replace the Host with APIM1's, and append APIM1's subscription-key query parameter if it is enabled var urlBuilder = new UriBuilder(url); // Replace the hostname with APIM's urlBuilder.Host = "<APIM1_host_name>.azure-api.net"; // Get the subscription-key if you enabled it in APIM portal var subscriptionKey = "<the_subscription_key>"; var subscriptionKeyQuery = $"subscription-key={subscriptionKey}"; urlBuilder.Query = string.IsNullOrEmpty(urlBuilder.Query) ? subscriptionKeyQuery : $"{urlBuilder.Query}&{subscriptionKeyQuery}"; var apim1Url = urlBuilder.Uri; // Start the WebSocket connection using (var client = new WebsocketClient(apim1Url)) { // ... } }
