HTTP/2, the modern successor to HTTP/1.1, introduces binary framing, header compression, multiplexing, server push, and other enhancements that dramatically reduce latency and improve efficiency, making web pages load faster and more reliably across browsers and servers that support the protocol.
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 examines the critical factors influencing web performance—including network latency, TCP/HTTP protocols, browser rendering, and server-side architecture—and provides practical optimization techniques such as TCP tuning, HTTP/2 adoption, resource compression, caching, load balancing, and distributed design to achieve fast, scalable web services.
This article explains the fundamentals of HTTP, covering client‑server interactions, page rendering flow, proxy roles, statelessness, request/response structures, common methods, limitations of HTTP/1.0, and the performance enhancements introduced by HTTP/2.
Google's gRPC 1.0 release brings high‑performance, multi‑language RPC support built on Protocol Buffers and HTTP/2, enabling loosely coupled, scalable backend systems for data centers, mobile apps, IoT, and microservices with improved efficiency, security, and ecosystem adoption.
This article examines how widespread HTTP/2 adoption changes front‑end architecture, demonstrates concrete speed improvements through multiplexing, priority, and server‑push with real‑world demos and HAR analysis, and explains which legacy optimizations become obsolete.
This article explains how HTTP/2 server push works, why it improves page load performance, and provides practical Node‑SPDY code examples for pushing assets, redirects, cache‑validation messages, and integrating Server‑Sent Events to notify clients of pushed resources.
This article explains the key innovations of HTTP/2—including binary framing, multiplexing, header compression, request priority, server push, and flow control—while also providing practical tools and experimental results that demonstrate its performance advantages over HTTP/1.1 and SPDY.
This article translates and expands a performance study that pits HTTPS, SPDY/3.1, and HTTP/2 against each other using Firefox and HttpWatch on Google UK's homepage, revealing trade‑offs in header compression, response size, connection multiplexing, and page‑load speed.
This article explains how to redesign an iOS app's network layer to fully exploit HTTP/2 by switching from NSURLConnection to NSURLSession, discusses centralized versus distributed API designs, data handling strategies, security with SSL pinning, and provides concrete code examples and batch request techniques.
This guide explains how HTTP/2 changes traditional front‑end performance tricks, covers browser support, TLS requirements, Server Push benefits, and provides a concise Nginx configuration example to enable HTTP/2 on your site.
HTTP/2 upgrades the foundational HTTP protocol by switching to binary framing, compressing headers with HPACK, enabling true multiplexing over a single TCP connection, and supporting server push, all of which dramatically improve network efficiency and reduce latency compared to the legacy HTTP/1.1.
This article explains how HTTP/2 replaces SPDY, introduces multiplexing, header compression and Server Push, and shows why many HTTP/1 optimization tricks become obsolete while still offering practical strategies for faster resource loading on modern web pages.
This article explains the concept of HTTP/2 server push, demonstrates how to implement it using the node‑spdy module with code samples for pushing assets, redirects, and SSE notifications, and discusses practical considerations and future possibilities for optimizing web performance.
gRPC, an open‑source RPC framework built by Google on HTTP/2 and Protocol Buffers, offers strong IDL capabilities, multi‑language support, and efficient streaming that reduce bandwidth, CPU usage, and battery drain, making it ideal for low‑latency, scalable backend and mobile client architectures.
