Skip to content

Add real-world use cases section to WebSocket docs #34960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions framework-docs/modules/ROOT/partials/web/websocket-intro.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -101,3 +101,10 @@ may preclude WebSocket interactions, either because they are not configured to p
`Upgrade` header or because they close long-lived connections that appear idle. This
means that the use of WebSocket for internal applications within the firewall is a more
straightforward decision than it is for public facing applications.

[[websockets-use-cases]]
=== Real-World Use Cases for WebSockets
* **Real-time Chat Applications:** Instant messaging depends on persistent connections for real-time delivery of messages.
* **Collaborative Tools:** Applications such as shared documents use WebSockets to synchronise changes in real time, allowing multiple users to collaborate simultaneously.
* **Online Games:** Multiplayer games rely on WebSockets for low-latency, real time communication between clients and servers.
* **Data Broadcast:** WebSockets provide a reliable and efficient way to push live data to users such as financial market updates and sports scores.