Tagged articles
real-time push
15 articles · Page 1 of 1
This comprehensive guide demonstrates why Server-Sent Events (SSE) is the superior choice over WebSocket for unidirectional server push scenarios like AI token streaming, covering Spring Boot integration patterns, production hardening (async thread pools, Nginx buffering, heartbeats, reconnection), and cluster deployment with Redis Pub/Sub.
AI streamingSSEServer-Sent Events
0 likes · 23 min read

This article compares SSE and WebSocket for server push, details SpringBoot integration with SseEmitter, WebFlux, and raw HttpServletResponse, provides a production-ready connection manager with heartbeat and clustering via Redis, and demonstrates AI streaming and real-time dashboard use cases.
AI streamingAsync ServletRedis Pub/Sub
0 likes · 29 min read

This article compares polling, WebSocket, and Server-Sent Events (SSE) for server-to-client real-time messaging, detailing SSE's lightweight HTTP-based design, automatic reconnection, and simpler server requirements, then provides a complete Node.js/Express and vanilla HTML/JavaScript demo.
EventSourceExpressHTTP Long Connection
0 likes · 13 min read

This article details implementing Server-Sent Events (SSE) in Spring Boot for real-time server-to-client push, covering SseEmitter endpoints, connection registry with cleanup, heartbeat, Last-Event-ID reconnection, cluster broadcasting via Redis Pub/Sub, Base64 binary transfer, and production tuning for Nginx and thread pools.
EventSourceRedis Pub/SubSSE
0 likes · 17 min read

This guide walks through why traditional polling or WebSocket solutions quickly break at scale, explains the Server‑Sent Events protocol, and presents a production‑grade architecture that combines Spring Boot 3, WebFlux, Kafka, Redis, and Kubernetes to deliver reliable, ordered, and observable one‑way push notifications for millions of concurrent users.
KafkaRedisSSE
0 likes · 43 min read

The article compares polling, WebSocket, and Server‑Sent Events (SSE) for server‑to‑client real‑time messaging, explains each method’s advantages and drawbacks, shows when to use SSE versus WebSocket, and provides a complete Node.js/Express demo with front‑end code.
ExpressHTMLJavaScript
0 likes · 13 min read

The article compares polling, WebSocket, and Server‑Sent Events for server‑to‑client real‑time messaging, explains the advantages and drawbacks of each, and provides a complete Node.js/Express and plain‑HTML demo showing how to implement SSE as a lightweight alternative to WebSocket.
EventSourceExpressNode.js
0 likes · 14 min read

This article introduces Spring's SseEmitter for server‑sent events, outlines its key features and use cases, and provides a complete end‑to‑end example—including Vue 3 front‑end setup, JavaScript client, and Spring Boot controller code—to enable real‑time message pushing between server and browser.
Server-Sent EventsSpring BootSseEmitter
0 likes · 8 min read

The talk explains how to build WeChat mini‑games from scratch using Cocos Creator and the platform’s cloud development suite—covering database, storage, cloud functions, real‑time push updates, and the MGOBE multiplayer engine with both frame and state synchronization options for rapid, serverless game deployment.
Cocos CreatorFrame SynchronizationMGOBE
0 likes · 18 min read

This article details the Mobile Service “秒开” project’s three‑step performance optimization, covering data‑driven monitoring, HTTP/2 features like header compression and multiplexing, long‑connection architecture with WebSocket, and an asynchronous caching component that together dramatically improve response times and reliability for mobile clients.
HTTP/2Mobile BackendWebSocket
0 likes · 13 min read


21CTOMar 18, 2019 · Frontend Development
This article reviews the evolution of web real‑time push techniques—polling, long‑polling, iframe streaming—and explains why WebSocket offers superior bidirectional communication, lower latency, and reduced bandwidth, while providing practical code examples for each method.
Long PollingPollingWebSocket
0 likes · 12 min read

The article details Meizu's massive real‑time push system handling 25 million online users and 600 million messages per minute, explains its four‑layer architecture, and shares how the team tackled phone power consumption, mobile network instability, massive connections, monitoring, and gray‑release deployment.
Gray Releasedistributed systemshigh concurrency
0 likes · 13 min read

The article details Meizu’s real‑time push system that supports 25 million online users and 6 million messages per minute, describing its four‑layer architecture, power‑saving strategies, network‑instability fixes, massive‑connection handling, monitoring practices, and gray‑release deployment techniques.
distributed systemshigh concurrencymonitoring
0 likes · 12 min read


21CTOMar 7, 2016 · Backend Development
This article details Meizu's real‑time push system handling 25 million online users and 50 billion daily PVs, describing its four‑layer backend architecture, challenges such as power consumption, mobile network instability, massive connections, and the monitoring and gray‑release strategies used to ensure reliability and performance.
Gray ReleaseLarge Scale Messagingbackend architecture
0 likes · 12 min read

The article recounts Meizu architect Yu Xiaobo's presentation on the company's real‑time push system, describing its massive scale, four‑layer backend architecture, challenges such as power consumption, mobile network instability, massive connections, and the monitoring and gray‑release strategies employed to ensure reliability.
Gray Releasehigh concurrencyload-balancing
0 likes · 12 min read
