0 views collected around this technical thread.
This article presents a step‑by‑step guide to building a Netty‑based WebSocket server in Java, covering server initialization, channel configuration, custom handlers, push‑message services, testing procedures, and includes complete source code, while also containing promotional material for unrelated AI services.
This tutorial explains how to use Netty to create a Java backend server with WebSocket support, covering server initialization, channel configuration, pipeline setup, custom handlers, and message‑push services, and includes complete code examples for each component.
This article reviews common real‑time message push techniques—including short and long polling, Server‑Sent Events, WebSocket, Netty, and MQTT—explaining their implementation ideas, core code snippets, advantages, and drawbacks so you can choose the most suitable solution for your business scenario.
The article explains RocksDB’s LSM‑based architecture, column‑family isolation, and snapshot features, and shows how Vivo’s VPUSH mapping service uses these capabilities to store billions of registerId‑to‑ClientId mappings with high‑concurrency, low‑cost, fault‑tolerant performance across multiple replicated servers.
The article explains RocksDB’s LSM‑based architecture, column‑family isolation, and snapshot features, and shows how Vivo’s VPUSH MappingTransformServer uses these capabilities with C++ code to store billions of registerId‑to‑ClientId mappings across multiple replicated servers for high‑concurrency, low‑latency, and fast service expansion.
Baidu’s full‑volume push system leverages a public‑mailbox architecture that merges a single shared mailbox with users’ private mailboxes during retrieval, enabling low‑disturbance, high‑speed delivery to over 600 million monthly active users while reducing write costs, as demonstrated by three pandemic‑policy messages reaching more than 200 million users within three days.
The team implemented SLA‑based, node‑level monitoring for mobile push messages—splitting the workflow, measuring latency, blocking volume, and success rates, isolating metrics with Spring AOP, and tracking third‑party vendors—resulting in clear latency standards, doubled peak throughput, faster issue resolution, and improved overall reliability.
This article explains various web message‑push techniques—including short and long polling, iframe streaming, Server‑Sent Events, MQTT and WebSocket—detailing their principles, advantages, drawbacks, and providing complete Spring Boot and JavaScript code examples for real‑time notification badges.
The SQLE 1.2204.0 release introduces an optimized SQL deployment workflow with approval steps, gh-ost dry‑run enhancements, real‑time message push for audit results, expanded permission controls, and a comprehensive list of new features, improvements, and bug fixes.
The article details the evolution and current architecture of the 58 Open Platform, covering its API gateway, multi‑protocol support, authentication mechanisms, distributed rate‑limiting, circuit‑breaking, thread‑pool isolation, and a Netty‑based real‑time message‑push system, while outlining future service‑marketplace and serverless plans.