---
title: "#websockets articles | Hashnode"
description: "Explore 594 articles tagged #websockets on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/websockets"
---

Tag

# #websockets

594 posts · 49 followers

[Abdul Rahman](https://hashnode.com/@abdulrdeveloper) · [1d ago](https://hashnode.com/posts/websockets-explained-real-time-chat/6afa9fc282ad3b9125769487)

### [WebSockets Explained: How Real-Time Chat Works and Why It’s Hard to Scale](https://blog.abdulrdeveloper.me/websockets-explained-real-time-chat?utm_source=hashnode&utm_medium=feed)

What WebSockets are and how real-time chat works, from the handshake and Socket.IO to Linux limits and scaling to a million connections.

16 min read · [blog.abdulrdeveloper.me](https://blog.abdulrdeveloper.me/websockets-explained-real-time-chat?utm_source=hashnode&utm_medium=feed)

[Leo Dahlgren](https://hashnode.com/@leodahlgren) · [3d ago](https://hashnode.com/posts/before-you-poll-50-markets-every-5-seconds-the-request-bandwidth-and-retry-budget-to-write-down-first/6af702db1c18049e5cda7e5e)

### [Before you poll 50 markets every 5 seconds: the request, bandwidth and retry budget to write down first](https://leodahlgren.hashnode.dev/before-you-poll-50-markets-every-5-seconds-the-request-bandwidth-and-retry-budget-to-write-down-first?utm_source=hashnode&utm_medium=feed)

Polling a REST endpoint is the first thing most of us build when we need market data. It's simple, stateless and easy to debug. It's also the design that quietly breaks when the market list grows from

4 min read · [leodahlgren.hashnode.dev](https://leodahlgren.hashnode.dev/before-you-poll-50-markets-every-5-seconds-the-request-bandwidth-and-retry-budget-to-write-down-first?utm_source=hashnode&utm_medium=feed)

[cryptolisting.ws](https://hashnode.com/@cryptolistingws) · [3d ago](https://hashnode.com/posts/parsing-multi-token-listing-announcements-comma-separated-tickers-and-listingtype-enums/6af6de1fadc15582b26a4d53)

### [Parsing Multi-Token Listing Announcements: Comma-Separated Tickers and listingType Enums](https://cryptolistingws.hashnode.dev/parsing-multi-token-listing-announcements-comma-separated-tickers-and-listingtype-enums?utm_source=hashnode&utm_medium=feed)

If a downstream parser reads only the first symbol out of an announcement, it silently misses tokens. Plenty of "list TOKEN1, TOKEN2 and TOKEN3" notices ship more than one coin in a single message, an

4 min read · [cryptolistingws.hashnode.dev](https://cryptolistingws.hashnode.dev/parsing-multi-token-listing-announcements-comma-separated-tickers-and-listingtype-enums?utm_source=hashnode&utm_medium=feed)

[Siebly](https://hashnode.com/@siebly) · [6d ago](https://hashnode.com/posts/bitget-books50-goes-incremental-on-1-december-keeping-a-local-order-book-in-node-js/6af301d64ef8af572d2c6ed2)

### [Bitget books50 goes incremental on 1 December: keeping a local order book in Node.js](https://siebly.hashnode.dev/bitget-books50-goes-incremental-on-1-december-keeping-a-local-order-book-in-node-js?utm_source=hashnode&utm_medium=feed)

What changes on the 50-level depth channel, and a small TypeScript-friendly handler that works before and after the switch

4 min read · [siebly.hashnode.dev](https://siebly.hashnode.dev/bitget-books50-goes-incremental-on-1-december-keeping-a-local-order-book-in-node-js?utm_source=hashnode&utm_medium=feed)

[Anish Ansari](https://hashnode.com/@anish78) · [Nov 9](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28)

### [System Design Drill Day 15: Real-Time Chat and Live Order Tracking](https://blog.anishansari.com.np/system-design-drill-day-15-real-time-chat-and-live-order-tracking?utm_source=hashnode&utm_medium=feed)

How to design real-time chat and live tracking: polling vs SSE vs WebSockets, a Redis pub/sub backplane, sequence numbers and resync.

6 min read · [blog.anishansari.com.np](https://blog.anishansari.com.np/system-design-drill-day-15-real-time-chat-and-live-order-tracking?utm_source=hashnode&utm_medium=feed)

[6](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28)

[Siebly](https://hashnode.com/@siebly) · [Nov 9](https://hashnode.com/posts/kucoin-api-javascript-tutorial-for-node-js-rest-and-websocket/6af2013b7003f418a735040d)

### [KuCoin API JavaScript tutorial for Node.js: REST and WebSocket](https://siebly.hashnode.dev/kucoin-api-javascript-tutorial-for-node-js-rest-and-websocket?utm_source=hashnode&utm_medium=feed)

Public and private REST calls, Classic WebSocket streams and a safe test order with kucoin-api

5 min read · [siebly.hashnode.dev](https://siebly.hashnode.dev/kucoin-api-javascript-tutorial-for-node-js-rest-and-websocket?utm_source=hashnode&utm_medium=feed)

[Siebly](https://hashnode.com/@siebly) · [Nov 9](https://hashnode.com/posts/okx-websocket-port-8443-is-retired-fixing-node-js-connections/6af1b2b112366c0ff9ab6428)

### [OKX WebSocket port 8443 is retired: fixing Node.js connections](https://siebly.hashnode.dev/okx-websocket-port-8443-is-retired-fixing-node-js-connections?utm_source=hashnode&utm_medium=feed)

OKX stopped accepting WebSocket connections on port 8443 on 31 October 2026 (Colo follows on 16 November). If your Node.js app still connects to wss://ws.okx.com:8443/..., the connection now fails. RE

2 min read · [siebly.hashnode.dev](https://siebly.hashnode.dev/okx-websocket-port-8443-is-retired-fixing-node-js-connections?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/okx-websocket-port-8443-is-retired-fixing-node-js-connections/6af1b2b112366c0ff9ab6428)

[Nhật Trường](https://hashnode.com/@nh4ttruong) · [Nov 7](https://hashnode.com/posts/getting-zalo-web-to-run-in-every-tab-with-one-socket/6aef5aea4085efce9fc2d4ec)

### [Getting Zalo Web to Run in Every Tab with One Socket](https://blog.nh4ttruong.me/getting-zalo-web-to-run-in-every-tab-with-one-socket?utm_source=hashnode&utm_medium=feed)

How Zalo Web keeps you to one tab, and how a small extension lets every tab share one connection

8 min read · [blog.nh4ttruong.me](https://blog.nh4ttruong.me/getting-zalo-web-to-run-in-every-tab-with-one-socket?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/getting-zalo-web-to-run-in-every-tab-with-one-socket/6aef5aea4085efce9fc2d4ec)

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [Nov 7](https://hashnode.com/posts/websockets-explained-real-time-data-without-polling/6aeea786aaac322776a911bd)

### [WebSockets Explained: Real-Time Data Without Polling](https://practicaldevblog.hashnode.dev/websockets-explained-real-time-data-without-polling?utm_source=hashnode&utm_medium=feed)

A customer adds a ceramic mug to their basket on a small shop's website, then waits. The order page says Processing, and nothing changes until they refresh. The server knew the order shipped ten minut

7 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/websockets-explained-real-time-data-without-polling?utm_source=hashnode&utm_medium=feed)

[Tushar Motwani](https://hashnode.com/@tusharmotwani) · [Nov 3](https://hashnode.com/posts/what-are-websockets-and-why-do-we-need-realtime/6ae9e02151c9b1b6e760a18d)

### [What are WebSockets and Why do we need Realtime](https://tusharmotwani.hashnode.dev/what-are-websockets-and-why-do-we-need-realtime?utm_source=hashnode&utm_medium=feed)

Real-time communication has always been a very important and useful tech for building low-latency collaborative products. While most people think that WebSockets are the only way to go real-time, the

14 min read · [tusharmotwani.hashnode.dev](https://tusharmotwani.hashnode.dev/what-are-websockets-and-why-do-we-need-realtime?utm_source=hashnode&utm_medium=feed)
