You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/socketio-overview.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Overview of Web PubSub for Socket.IO
3
-
description: Get an overview of Azure Web PubSub support for the open-source Socket.IO library.
2
+
title: Overview Socket.IO on Azure
3
+
description: Get an overview of Azure's support for the open-source Socket.IO library.
4
4
keywords: Socket.IO, Socket.IO on Azure, multi-node Socket.IO, scaling Socket.IO
5
5
author: kevinguo-ed
6
6
ms.author: kevinguo
@@ -9,27 +9,25 @@ ms.service: azure-web-pubsub
9
9
ms.topic: how-to
10
10
---
11
11
12
-
# Overview of Web PubSub for Socket.IO
12
+
# Overview Socket.IO on Azure
13
13
14
14
> [!NOTE]
15
-
> Web PubSub for Socket.IO feature is in public preview. We welcome any feedback and suggestions. Please reach out to the service team at [email protected].
15
+
> The support of Socket.IO on Azure is in public preview. We welcome any feedback and suggestions. Please reach out to the service team at [email protected].
16
16
17
-
Web PubSub for Socket.IO is a fully managed cloud offering for [Socket.IO](https://socket.io/). Socket.IO is a widely popular open-source library for real-time messaging between clients and a server. Web PubSub for Socket.IO is a feature of the Azure Web PubSub service.
17
+
Socket.IO is a widely popular open-source library for real-time messaging between clients and a server. Managing stateful and persistent connections between clients and a server is often a source of frustration for Socket.IO users. The problem is more acute when multiple Socket.IO instances are spread across servers.
18
18
19
-
Managing stateful and persistent connections between clients and a server is often a source of frustration for Socket.IO users. The problem is more acute when multiple Socket.IO instances are spread across servers.
20
-
21
-
Web PubSub for Socket.IO removes the burden of deploying, hosting, and coordinating Socket.IO instances for developers. Development teams can then focus on building real-time experiences by using familiar APIs from the Socket.IO library.
19
+
Azure provides a fully managed cloud solution for [Socket.IO](https://socket.io/). This support removes the burden of deploying, hosting, and coordinating Socket.IO instances for developers. Development teams can then focus on building real-time experiences by using familiar APIs from the Socket.IO library.
22
20
23
21
## Simplified architecture
24
-
Web PubSub for Socket.IO removes the need for an "adapter" server component when scaling out a Socket.IO app, allowing the development team to reap the benefits for a simplified architecture.
22
+
This feature removes the need for an "adapter" server component when scaling out a Socket.IO app, allowing the development team to reap the benefits of a simplified architecture.
25
23
26
24
:::image type="content" source="./media/socketio-service-internal/typical-architecture-managed-socketio.jpg" alt-text="Screenshot of a typical architecture of a fully managed Socket.IO app.":::
27
25
28
26
## Benefits over hosting a Socket.IO app yourself
29
27
30
-
The following table shows the benefits of using the fully managed Azure service.
28
+
The following table shows the benefits of using the fully managed solution from Azure.
31
29
32
-
| Item | Hosting a Socket.IO app yourself | Using Web PubSub for Socket.IO|
30
+
| Item | Hosting a Socket.IO app yourself | Using Socket.IO on Azure|
33
31
|------------|------------|------------|
34
32
| Deployment | Customer managed | Azure managed |
35
33
| Hosting | Customer needs to provision enough server resources to serve and maintain persistent connections | Azure managed |
@@ -44,7 +42,7 @@ A common approach to meeting the concurrency and latency challenge is to [scale
44
42
45
43
:::image type="content" source="./media/socketio-overview/typical-architecture-self-hosted-socketio-app.jpg" alt-text="Diagram of a typical architecture of a self-hosted Socket.IO app.":::
46
44
47
-
With Web PubSub for Socket.IO, you're freed from handling scaling issues and implementing code logic related to using an adapter.
45
+
With Socket.IO on Azure, you're freed from handling scaling issues and implementing code logic related to using an adapter.
0 commit comments