This article walks through the design and implementation of a TCP long‑connection communication scheme using Netty and Spring Boot 2.2.0, covering project architecture, module layout, message flow, detailed code explanations, testing procedures, and deployment considerations.
This guide introduces GatewayWorker, a PHP‑based distributed TCP long-connection framework, explains its Gateway-Worker process model, and provides step-by-step Windows demo instructions for both TCP and WebSocket protocols, highlighting deployment, code changes, testing procedures, and suitable real-time communication scenarios.
This article explains the fundamental differences between long-lived and short-lived network connections, covering their operation processes, resource consumption, typical use cases, and impact on stability and fault tolerance, helping developers choose the right approach for their applications.
The article details a Golang‑based high‑throughput long‑connection service for live‑streaming, describing its five‑layer architecture, multi‑protocol support, load‑balancing, message‑queue decoupling, aggregation with brotli compression, multi‑region deployment, priority channels, and future enhancements for observability and intelligent endpoint selection.
This article details Baidu’s internally built unified long‑connection service in Go, covering its motivation, architecture, functional implementation, performance optimizations, multi‑business support, deployment strategy, and lessons learned for delivering secure, high‑concurrency, low‑latency real‑time connectivity across mobile applications.
Baidu’s Go‑based unified long‑connection service delivers secure, high‑concurrency, low‑latency connections for multiple Baidu apps through a four‑layer architecture (SDK, control, access, routing), employing goroutine pooling, two‑layer connection models and binary routing to support tens of millions of concurrent users and million‑level QPS, while simplifying integration and reducing maintenance costs.
This article explains TCP connection basics, the three‑way handshake and four‑way termination, compares short and long connections, discusses keep‑alive mechanisms, and outlines when to use each approach in network and HTTP communication.
TCP connections can be either short-lived, closing after a single request‑response cycle, or long-lived, staying open for multiple exchanges; this article explains their handshake processes, advantages, drawbacks, typical use cases, reasons long connections drop, and practical strategies such as keepalive and reconnection to maintain reliability.
This article explains the fundamentals of TCP connections, detailing the three‑way handshake, four‑step termination, the differences between short‑lived and persistent (long) connections, their advantages, keep‑alive mechanisms, and practical guidelines for choosing the appropriate connection type in various network scenarios.
This article examines the evolution of long‑connection technology for mobile apps, outlines Baidu’s unified long‑connection service architecture, details the iOS SDK’s design choices—including protocol selection, DNS optimization, token handling, heartbeat and reconnection mechanisms—and demonstrates its real‑time messaging use cases within the Baidu App.
This article explains the differences between short and long connections, why long‑connection services need load balancing, and presents practical strategies for connection‑level balancing, handling server restarts, heterogeneous hardware, and scaling challenges.
This article explains how to assemble a production‑grade service registry by analyzing requirements, defining registration/discovery interfaces, comparing push and health‑check mechanisms, selecting long‑connection technologies, and choosing data‑storage and high‑availability strategies, all illustrated with JSON examples and design guidelines.
This article explains how to build a high‑concurrency Netty long‑connection server cluster using Redis publish/subscribe to forward messages across nodes, detailing the background, technology choices, architecture, and implementation steps for a microservice‑based backend system.
This article walks through the challenges and solutions for building a high‑performance long‑connection service with Netty, covering Netty basics, non‑blocking I/O, sample Java NIO and Netty code, Linux kernel tuning, QPS optimization, data‑structure tweaks, GC adjustments, and the final performance results.
This article explains a technique for writing long‑TCP connection business code on mobile devices that is as efficient and concise as short‑link code, using request_id mapping, protobuf messages, and a lightweight SendCore layer with timeout handling.
The article details Vivo’s push notification platform, describing its evolution from cloud‑based beginnings to a self‑built, three‑region architecture that supports over 1 million concurrent connections, billions of daily messages, and incorporates optimizations such as adaptive heartbeats, advanced load‑balancing, distributed caching, multi‑layer rate limiting, circuit‑breaker mechanisms, and comprehensive content security.
This article explains how to build a scalable long‑connection service using Netty, covering the underlying concepts, Linux kernel tuning, code examples for Java NIO and Netty, performance bottlenecks such as QPS, data‑structure and GC issues, and practical optimization techniques to achieve hundreds of thousands of concurrent connections.
This article presents the design, implementation, and performance evaluation of a Netty‑based WebSocket long‑connection gateway that centralizes session management, decouples business logic, supports horizontal scaling, and provides monitoring and alerting for high‑throughput real‑time data push in iQIYI’s platform.
This article explains HTTP’s key characteristics, compares short‑lived and persistent connections, and explores related concepts such as head‑of‑line blocking, concurrency, and domain sharding, providing readers with a comprehensive understanding of how HTTP manages connections and performance.
The article explains Nacos 2's new long‑connection model built on gRPC, its performance gains over Nacos 1.x, compatibility details for configuration and discovery, Spring Cloud Alibaba integration, and provides download links and reference resources.
This article explains the challenges of server‑push in HTTP, reviews WebSocket as the mainstream solution, and details the design, implementation, session management, monitoring, and performance testing of a Netty‑based distributed WebSocket long‑connection gateway used at iQIYI.
iQIYI built a Netty‑based WebSocket long‑connection gateway that centralizes session management, uses RocketMQ for cluster‑wide broadcast, provides a simple HTTP push API, scales horizontally to millions of connections, integrates Prometheus/Grafana monitoring, and dramatically cuts development effort for real‑time features such as comments and authentication.
Xianyu improved its online IM channel stability by adding heartbeat‑based connection monitoring, rapid reconnection, ACK‑driven retry queues stored in Alibaba Cloud Table Store, and adaptive delay strategies, which together cut ACC compensation arrival time by 75% (from 60 to 15 minutes) and dramatically reduced user complaints.
This article explains the core characteristics of the HTTP protocol—including its flexibility, reliability, application‑layer nature, request‑response model, and statelessness—and then details short and long connection management, related header fields, head‑of‑line blocking, and practical performance‑enhancing techniques such as concurrent connections and domain sharding.
This article explains HTTP's core characteristics—flexibility, reliability, application‑layer nature, request‑response model, and statelessness—then dives into short‑ and long‑connection management, head‑of‑line blocking, and practical optimization techniques such as concurrent connections and domain sharding.
This article details the architecture, protocol design, permission control, reliability mechanisms, and scaling strategies of a long‑connection gateway built with OpenResty, Kafka, and Redis, illustrating how to share persistent connections across multiple business services while ensuring high performance and fault tolerance.
This tutorial explains how to use the Workerman PHP socket framework and GatewayWorker to replace HTTP long‑polling with WebSocket‑based real‑time communication, covering protocol basics, short vs. long connections, integration with MVC frameworks, and complete client‑ and server‑side code examples.
The article presents Hermes, a lightweight and highly reliable mobile push system built with MQTT and Protocol Buffers, detailing its background, technology selection, architecture, heartbeat and reconnection strategies, future optimizations, and practical results that achieve over 99% message delivery rate.
Zhihu’s infrastructure team designed a high‑performance, scalable long‑connection gateway that decouples business logic via publish‑subscribe, leverages OpenResty, Kafka, and Redis, implements fine‑grained ACL, sliding‑window flow control, and ensures message reliability and horizontal scalability for millions of concurrent devices.
The article summarizes the second 58.com instant‑messaging technology salon, detailing the architecture, high‑performance long‑connection design, multi‑thread socket models, read‑write diffusion storage strategies for single‑ and group‑chat, message synchronization mechanisms, and the IM SDK framework for audio‑video communication.
Over three years, Meitu’s long‑connection service “bifrost,” built in Go with MQTT, cut memory use from 22.3 GB to 5.1 GB for 210 k connections—and about 10 GB for a million—by tuning buffers, reducing allocations, employing memory pools, and replacing a goroutine‑per‑connection model with an epoll‑driven event architecture.
This article explains how Zhihu designed a scalable long‑connection gateway that decouples business logic via a publish‑subscribe model, implements ACL‑based authorization, ensures message reliability with acknowledgments and sliding windows, and leverages OpenResty, Redis, and Kafka for load‑balanced, fault‑tolerant backend services.
The article explains how MaFengWo built a custom travel transaction system that uses multi‑order distribution, a grab‑pool message queue, concurrency‑controlled locking, and long‑connection notifications to efficiently match personalized travel requests with multiple suppliers, boosting conversion rates and platform performance.
Meipai’s live‑stream bullet‑comment platform progressed from an initial HTTP‑polling design supporting one million users, through a high‑availability dual‑room architecture, to a scalable long‑connection system with gRPC routing, dynamic degradation, and caching, solving message ordering, Redis bottlenecks, and ensuring seamless user experience.
The article explains the challenges of protecting long‑connection services from abuse and presents a one‑time secure token architecture—including gateway SDK, token generation, Redis caching, and verification modules—to ensure authentication, prevent replay attacks, and improve service robustness.
This article explains the principles of TCP long connections, compares NIO and BIO models, and describes how Android applications can implement and share persistent connections using AIDL, process sharing, and a dedicated SDK to support push, IM, and other real‑time services.
Meituan‑Dianping’s high‑availability mobile network optimization combines short‑connection tactics—domain merging and IP‑direct selection—to cut DNS lookups, with a proxy‑long‑link architecture (CIP and Tencent WNS) that provides DNS‑independent, multiplexed TCP links, improving latency, success rates, and offering fallback mechanisms for robust app performance.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, and compares long and short connections—including their TCP handshakes, keep‑alive mechanisms, advantages, disadvantages, and appropriate usage scenarios for web and database communications.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, and compares long‑lasting persistent connections with short‑lived ones, covering their handshakes, advantages, disadvantages, and appropriate usage scenarios.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, compares short and long connections in HTTP/1.0 and HTTP/1.1, and discusses the advantages, disadvantages, and appropriate use cases for each connection type.
An in‑depth look at 360’s long‑connection push platform built with Go, covering system architecture, key performance indicators, scalability challenges, optimization strategies, operational practices, and practical Q&A for building reliable, high‑throughput messaging services.
This article details the architecture, key performance metrics, and optimization strategies of 360’s high‑availability long‑connection push system built with Go, covering connection capacity, memory usage, throughput, deployment components, client SDK considerations, and operational challenges such as GC pauses and load balancing.
This article explains the differences between long and short TCP/IP connections, outlines three major communication models (server/client, connection type, and send/receive mode), describes synchronous and asynchronous transmission, and reviews various message formats and read/write strategies to help developers design robust network programs.
