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.
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.
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.
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.
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.
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.
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.
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.
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.
