Real-time information sharing for enterprises, complete package of sky blue signal!

Microsoft official public number. Give all creatures power and achieve extraordinary achievements! Microsoft is committed to using technology to change the world and help businesses achieve digital transformation.

(Reading time of this article: 7 minutes) The Human Resources Department posted a notice at the entrance of each office asking employees to scan the code and fill out a questionnaire to report their health status. Team leaders send various e-mails to inform relevant members of their work arrangements during the outbreak. The senior management assistant called different departments for three days and two days to convey the boss's latest instructions. The staff set up more than n groups with different arrangements to discuss the epidemic, gossip and what to eat for lunch. In this special period, all kinds of news are flying around, everyone is exhausted while paying attention. How to understand the health information of all employees in real-time at the key period of orderly recovery of the epidemic? How to get the abnormal information reported by employees first and how to publish the latest epidemiological policies to all levels. These are the issues that companies are most concerned about, of course, many companies are considering integrating these functions into their internal office systems. Open source project architecture This open source project is mainly based on the Azure SignalR service, which can help us easily add real-time communication capabilities to network applications. High-frequency data updates (such as games, voting, voting), dashboards, monitoring, chat, real-time map positioning, real-time targeted advertising, and even IoT and Internet devices, as well as event-based real-time triggers and other scenarios are all services that the service can Great progress scene. At the same time, the service can be seamlessly integrated with other Azure services, extending many practical capabilities. This project mainly implements application scenarios based on two types of users: corporate employees: when employees work on their own web pages, applets, and mobile applications, they can receive real-time push of corporate epidemic information in real time. Enterprise management users: Managers can customize messages to send epidemic management information to each employee's client in real time. At the same time, they can also monitor employee feedback on the epidemic situation information and employee epidemic statistics in real time at the monitoring station. In fact, this open source project also includes many interesting function implementations, such as reporting the epidemic information to the company's voice, real-time reporting of epidemic video comments, and real-time statistics of employees' feedback on epidemic information. Open source project architecture: employee / administrator interface: Employee function page, including video, video interception, real-time statistics histogram, and epidemic information notification bar; administrator management page contains information release text box. Information sent by the administrator is broadcast to clients through the Azure SignalR service. When employees access the feature page from their computer and mobile device, they can receive messages from the management station in real time. At the same time, you can also send a barrage in the video, and the barrage will be broadcast in real time to all users who visit the page. Real-time messages are received and sent through the Azure SignalR service. For the real-time epidemic information sent by the administrator, you can directly call the Azure Cognitive Services application programming interface to implement text voice broadcast. In this demo code, if a business wants to apply the real-time outbreak notification feature, you can quickly add existing code to existing features by adding few code changes to existing feature pages (possibly websites or WeChat, or mobile applications using JS technology) Add real-time outbreak notification function. Why Choose Azure Signar Service Next, let's see why this open source project chose Azure Signar to implement the core functions of the project. Sky blue signals are at the heart of real-time message notifications. The user only needs to create an instance and can call it in the program.

Of course, enterprises can also choose real-time communication services other than Azure SignalR, but the following problems will be added: when real-time messages are notified, they need to be reflected immediately when there are messages in the background and front-end. How to ensure that the information is sent in real time? The customer network is unstable. How to ensure the customer's application experience, that is, how to solve the problem of information accessibility after network interruption and recovery? How to achieve real-time synchronization of streaming media data, such as popular video streaming? (Different from processing block text messages, you also need to consider how to package when processing streaming data.) Users may have adopted various devices or browsers. How to perfectly adapt to different clients? The company's existing applications are already microserviced. Different teams use different language platforms. How do different services smoothly interface with the real-time communication module? Real-time communication was not considered when the system was implemented, and the business unit suddenly requested to go online within one or two days. How to implement it quickly? If user access increases dramatically, how can we make the real-time communication module flexible and scalable and ensure session state? How to ensure high availability in the event of software and hardware failures on the server? In other words, if there is no such real-time communication service, developers must use basic communication technologies (such as WebSocket) to achieve high performance, high concurrency, flexible expansion and stable operation of real-time communication services. Azure SignalR service is such a service for real-time communication in enterprises. Used users. Network signal or. The core signal of the network may understand that the signal (already open source on GitHub) is a component dedicated to real-time communication, which helps developers solve many issues that need to be considered in real-time communication. However, developers still need to consider details related to scalability, high availability, cross-platform, and more. As a serverless service, Azure SignalR minimizes the difficulty of real-time communication scenarios. The server-side implementation of the Azure SignalR service is actually a PaaS implementation of Signar. The signalman (is filming. In fact, the network core signal is an example. The network signal is a component that includes a server and a client. It establishes a long connection between the server and the client and provides a call from the server API for client-side JavaScript functions. SignalR ensures that once the server receives an update of information, it will pass it to the client in a timely manner. To this end, SignalR provides the following functions to meet real-time communication scenarios: Server and client connection management, including connection creation and disconnection, and automatic connection management. Send messages to all connected clients at the same time, these messages may come from the client or server, or from a third party. Send a message to a specific client or client group. Increasing traffic is adjustable. Considering the characteristics of different browsers used by the client or the particularity of the device, SignalR provides three real-time communication technologies: WebSocket, server sending events, and long polling. Developers can choose a fixed communication method based on the target customer, or they can automatically choose the option that best suits the current customer for SignalR according to specific rules. This can greatly save developers time and effort in making the application compatible with various browsers. SignalR still requires developers to deal with sticky sessions in multi-node deployments. For example, if client 1 wants to communicate with client 3 in real time, it is necessary to implement a sticky session between server 1 and server 2. In addition, developers also need to consider how to manage server-side TCP resources (SignalR gives priority to long connections. If users have a lot of access, they will soon use a single server TCP connection). When the connection is bottlenecked or idle, how to flexibly expand and reduce the number of servers is a problem that developers need to spend a lot of energy to solve. Azure SignalR service perfectly solves these two problems. The Azure SignalR service enables developers to quickly implement real-time communication capabilities in new or existing applications. WebSocket, server sending events, and long polling. Developers can choose a fixed communication method based on the target customer, or they can automatically choose the option that best suits the current customer for SignalR according to specific rules. This can greatly save developers time and effort in making the application compatible with various browsers. SignalR still requires developers to deal with sticky sessions in multi-node deployments. For example, if client 1 wants to communicate with client 3 in real time, it is necessary to implement a sticky session between server 1 and server 2. In addition, developers also need to consider how to manage server-side TCP resources (SignalR gives priority to long connections. If users have a lot of access, they will soon use a single server TCP connection). When the connection is bottlenecked or idle, how to flexibly expand and reduce the number of servers is a problem that developers need to spend a lot of energy to solve. Azure SignalR service perfectly solves these two problems. The Azure SignalR service enables developers to quickly implement real-time communication capabilities in new or existing applications. WebSocket, server sending events, and long polling. Developers can choose a fixed communication method based on the target customer, or they can automatically choose the option that best suits the current customer for SignalR according to specific rules. This can greatly save developers time and effort in making the application compatible with various browsers. SignalR still requires developers to deal with sticky sessions in multi-node deployments. For example, if client 1 wants to communicate with client 3 in real time, it is necessary to implement a sticky session between server 1 and server 2. In addition, developers also need to consider how to manage server-side TCP resources (SignalR gives priority to long connections. If users have a lot of access, they will soon use a single server TCP connection). When the connection is bottlenecked or idle, how to flexibly expand and reduce the number of servers is a problem that developers need to spend a lot of energy to solve. Azure SignalR service perfectly solves these two problems. The Azure SignalR service enables developers to quickly implement real-time communication capabilities in new or existing applications.

With the Azure Signar service, each client's real-time communication connection will be connected to the Azure Signar service. As a PaaS service, Azure SignalR service can flexibly expand and contract according to the number of customers to achieve sticky session capabilities. Applications that require real-time communication need only maintain a small number of fixed connections to the Azure SignalR service, thereby separating the real-time communication module from the application server. Azure SignalR service has built-in failover capabilities to ensure service stability and guarantees a 99.9% service level agreement guarantee. Client Connection When the client establishes a real-time communication connection, it will redirect on the application side, completing the connection with Azure Signer: 1. The client connects to the application server. 2. The application server requests a token from the Azure SignalR service. 3. The azuresignalr service returns a token after verifying the server's request. 4. After obtaining the authorization of the Azure SignalR service, the application server redirects the client's connection request to the Azure SignalR service and attaches the token of the Azure SignalR service. 5. The client uses the obtained Azure Signar service token to connect to the redirected Azure Signar service address. In this case, adding real-time communication modules requires only a few changes to the application. For developers, it is not necessary to build a complete real-time communication service framework from scratch. In terms of support for different languages, Azure SignalR service provides customers with ASP.Net core, ASP. Net, JavaScript, Java, and REST application programming interfaces to facilitate developers to use their familiar development language for real-time communication development. More Application Scenarios With Azure SignalR services, enterprises can not only quickly build real-time messaging platforms during wars and epidemics, but also quickly build real-time communication capabilities in many business scenarios that require real-time communication. For example, perform one-to-one, one-to-many, and many-to-many real-time messaging scenarios. Typical scenarios include chat rooms, game real-time chat, game real-time scoreboards, team collaboration (such as meeting whiteboards), and real-time interaction (including text, voice, and video) in online education scenarios. Real-time status notifications and event updates. Typical scenarios include financial market change information, financial product price reminders, real-time location sharing of logistics, real-time update of IoT device status, and smart home (city). Need low-latency real-time streaming media, such as real-time games, online auctions, stock recommendations, real-time videos, and more. Finally, it should be noted that the Azure SignalR service not only supports the integration and use of various development platforms, but also supports various client types such as browsers, desktop applications, mobile applications, server-side processes, IoT devices, games Host, etc. Here is the technical dry goods of welfare time today. For more information and usage of the Azure SignalR service, please check the official documentation or leave a message to contact us. Of course, we even encourage those who haven't tried the "anti-epidemic open source project" to click the end of the article to read the original text, view the GitHub open source project documentation, communicate and discuss with us, and millions of Azure welfare heartwarming gifts. Finally, we launched a free technical course for this project. Everyone is welcome to scan the QR code below and watch the study on Wednesday. For more information and usage of the SignalR service, please see the official documentation or leave a message to contact us. Of course, we even encourage those who haven't tried the "anti-epidemic open source project" to click the end of the article to read the original text, view the GitHub open source project documentation, communicate and discuss with us, and millions of Azure welfare heartwarming gifts. Finally, we launched a free technical course for this project. Everyone is welcome to scan the QR code below and watch the study on Wednesday. For more information and usage of the SignalR service, please see the official documentation or leave a message to contact us. Of course, we even encourage those who haven't tried the "anti-epidemic open source project" to click the end of the article to read the original text, view the GitHub open source project documentation, communicate and discuss with us, and millions of Azure welfare heartwarming gifts. Finally, we launched a free technical course for this project. Everyone is welcome to scan the QR code below and watch the study on Wednesday.