A 90‑minute live discussion with three industry experts dissects why AI agents often stall after a successful demo, examining protocol collaboration, self‑evolution capabilities, and token‑cost control, while offering concrete engineering, management, and business‑value insights for enterprise AI adoption.
The IETF’s new RFC 10008 defines a QUERY HTTP method that combines GET’s safety and idempotence with POST’s ability to carry large request bodies, offering a standardized way for API designers to send complex, read‑only queries without the limitations of URL‑encoded parameters.
A technical review reveals that Telegram’s MTProto protocol exposes a permanent 64‑bit device identifier (auth_key_id) in clear text, enabling passive observers—including ISPs, mobile carriers, and state surveillance—to track users across app restarts, IP changes, VPNs, and even Tor, rendering secret chats and PFS ineffective.
MCP (Model Context Protocol) is an open standard that lets AI applications connect to external systems through a unified client‑server model, exposing Tools, Resources, and Prompts, while addressing security, permission, and audit concerns to make large‑model deployments more reusable and controllable.
Google’s open‑source A2A (Agent‑to‑Agent) protocol, unveiled at Google Cloud Next 2025, defines a standardized, secure, Web‑based framework that lets heterogeneous AI agents discover each other, negotiate interactions, and manage cross‑agent tasks, supporting multimodal communication, long‑running jobs, and push notifications.
This article explains what TCP sticky packets are, why they occur due to rapid sending, slow reading, or buffer limits, and presents practical solutions such as fixed‑length framing, delimiters, padding, and the Nagle algorithm to ensure reliable data parsing.
The article walks through every stage of a web request—from IPv4 addressing, NAT, and DNS resolution through CDN proximity and TCP stream handling, to HTTP framing, CGI versus FastCGI processing, stateless versus stateful server models, and finally database scaling techniques such as sharding and Redis caching.
The article reviews ten years of RDMA development, tracing its origins, the rise and pitfalls of RoCEv1/v2, alternative approaches like iWARP and Cisco usNIC, and recent modernizations such as AWS SRD, Google Falcon and UltraEthernet, highlighting why protocol design choices have repeatedly stalled industry progress.
The Bilibili video template system combines theme‑based editing, a layered architecture, and a cross‑platform Protobuf protocol to enable PGC and UGC creators to produce, review, distribute, and consume richly‑featured videos with standardized media formats, modular plugins, AI integration, and robust quality assurance.
The article reviews the rapid growth of audio‑video applications, categorizes media transmission scenarios into generic VoD, RTC and Live, examines Kuaishou’s optimization practices with protocols such as KTP, LAS, KLP and AAS, and introduces the next‑generation CMTP protocol designed to unify and extend these solutions across all use cases.
This article explains how Tencent’s internal high‑availability service curriculum emphasizes architecture boundaries, unified protocol definitions using JCE, a unified PushAPI, monitoring and feedback mechanisms, and the organizational impact of aligning system and team boundaries to achieve scalable, reliable backend services.
This article walks through practical trade‑offs in designing a Go microservice framework, covering protocol choices, data transport, network handling, serialization methods, service registry options, routing algorithms, and rate‑limiting strategies, while highlighting real‑world implementation details and pitfalls.
This article explains Baidu’s custom bdtls security communication protocol for mini‑programs, detailing its TLS 1.3‑based architecture, DHE‑RSA key exchange, AES‑GCM encryption, implementation on both server and client sides, and the strategies used to achieve strong security, low latency, high availability, and extensibility.
Baidu’s bdtls protocol adapts TLS 1.3 for mini‑programs, delivering mutual authentication, AES‑128‑GCM encryption, RSA‑signed Diffie‑Hellman key exchange, sub‑10 % handshake latency, and extensible multi‑business support to defend against static, dynamic and cheating attacks while ensuring high availability.
This article explains the principles of protocol design, covering layered architecture, the differences between text, binary, and streaming XML application protocols, security layer options beyond SSL, and transport layer choices, providing concrete examples and code snippets to illustrate each concept.
This article explains the motivation, design principles, model architecture, and implementation challenges of rebuilding ByteDance's Node.js RPC system, covering DDD‑based decomposition, protocol and connection abstractions, multi‑protocol nesting, client/server creation APIs, and performance‑optimized context extensions.
The article analyzes WeChat's success by detailing its three‑pronged strategy of precise product timing, agile project management, and robust technical support, and explains how the team applies agile attitudes, modular design, extensible protocols, disaster‑recovery mechanisms, and fine‑grained monitoring to operate a massive, highly available system.
The article analyzes the core technical challenges of mobile instant‑messaging services—battery consumption, limited traffic, unreliable networks—and explains how WeChat and Momo design hybrid short‑/long‑connection protocols, use protobuf, intelligent routing, load‑balancing, sharding and distributed algorithms to achieve high reliability and scalability.
This article explains the fundamentals of RPC protocols, compares common designs such as HTTP/1.1, RESP, HTTP/2, and gRPC, and outlines the motivations and key features of Dubbo 3.0’s next‑generation protocol for better performance, extensibility, and cross‑language support.
This article explains SkyWalking’s modular, protocol‑oriented and lightweight architecture, its core components, design principles, and advantages such as cross‑environment consistency, easy maintenance, high performance, and extensibility for both traditional and cloud‑native systems.
This article explains the design and implementation of an ABT (Auto‑Bidding Test) system that automates A/B decision cycles, covering client SDK architecture, protocol specifications, data‑point collection, resource‑placement experiments, and home‑page integration to accelerate product growth.
This guide walks through designing a Java RPC framework from the user's viewpoint, covering interface definition, client stub generation with dynamic proxies, flexible protocol and service discovery layers, server request handling, and key implementation steps, illustrated with diagrams and code snippets.
This article delves into the internal design of NVMe over Fabrics, explaining its encapsulation scheme, command mapping, discovery mechanisms, and the extended Connect and Property commands that enable efficient, low‑latency storage networking across diverse fabric transports.
This article provides a comprehensive overview of the MQTT protocol, covering its origin, design goals, packet structure—including fixed and variable headers, control types, flags, remaining length, and payload—while highlighting its suitability for IoT and limitations for large data transfers.
This article dissects RocketMQ’s Remoting communication module, covering its architecture, class hierarchy, custom protocol design, message encoding/decoding, synchronous, asynchronous and one‑way communication modes, and the detailed client‑server interaction flow including timeout handling and callback execution.
This article explores the challenges of JavaScript‑Native communication in Android WebView, compares Android‑to‑JS and JS‑to‑Android invocation methods, and presents a custom, secure, and extensible JS bridge framework with protocol design, interceptors, annotations, and implementation examples for hybrid app development.
This article distills practical design decisions for modern encrypted communication protocols—covering algorithm selection, versioning, PKI choices, library alternatives, replay protection, performance tuning, and latency considerations—while providing a concise appendix of fundamental cryptographic concepts and key references.
This article explains the layered design of TLS, details the cryptographic primitives and cipher suites it uses, and provides guidance on selecting secure configurations while avoiding unsafe legacy algorithms.
This article explores the TLS protocol in depth, outlining its design objectives, cryptographic foundations, historical evolution, detailed handshake and record layer mechanisms, security analyses, common pitfalls, and lessons for designing robust modern encrypted communication protocols.
This article dissects the design of 58 Daojia’s universal real‑time messaging platform, detailing the challenges of end‑to‑cloud, cloud‑to‑end, and end‑to‑end communication, the shortcomings of traditional HTTP and push solutions, and the optimized TCP, message‑bus, RPC, and protocol extensions that achieve scalability, reliability, and cross‑account chat.
This article provides an in‑depth technical overview of Meizu's cloud sync service, covering its business scenarios, the evolution of its core SyncML‑based protocols, modular architecture across multiple data centers, performance optimizations such as traffic reduction and connection handling, as well as high‑availability, security, and future SDK‑API extensions.
This article details the design and implementation of 58’s real‑time messaging platform, covering its business background, overall architecture, protocol design for extensibility and debugging, and solutions for fast TCP reconnection to ensure stable, high‑throughput delivery for intra‑city freight services.
This article details Meizu's cloud synchronization service, covering its custom MZ‑SyncML protocol, semi‑sync mechanisms, file and one‑sync protocols, failure handling, service architecture, modular design, massive data routing, multi‑datacenter deployment, traffic optimization, and practical lessons learned.
This article analyzes the architectural choices behind WeChat and Momo instant‑messaging services, covering battery and traffic constraints, network reliability, the shift from XMPP to proprietary long/short connections, protocol design with protobuf, and operational strategies for scaling massive user bases.
This article explains the fundamentals of instant messaging, its system characteristics, protocol layers (application, security, transport), practical protocol examples, and a detailed real‑time web chatroom design using HTTP long‑polling and backend architecture considerations.
