0 views collected around this technical thread.
Discover the five crucial differences between the classic requests library and the modern httpx client—including async support, HTTP/2, type hints, streaming APIs, and client lifecycle management—so you can choose the right tool for high‑performance Python backend projects.
This article examines gRPC’s implementation principles, multi‑language support, Protocol Buffers foundation, advantages and disadvantages, and provides a C++/Go demo illustrating its cross‑language capabilities within cloud‑native environments, including project structure, code snippets, and discussion of HTTP/2 transport.
gRPC can halve request latency compared to REST+JSON by leveraging HTTP/2’s multiplexed connections and the compact binary Protobuf format, which reduces payload size and speeds serialization, though it introduces complexities like load balancing, debugging, and contract management.
The article explains why browsers limit concurrent connections per domain for performance and security reasons, compares HTTP/1.1 and HTTP/2 handling of these limits, and outlines practical frontend optimization strategies such as domain sharding, CDN usage, resource bundling, and lazy loading.
This article introduces Tonic, a Rust gRPC framework, explains its core features, components, and provides detailed, code‑rich instructions for building both server and client applications, while highlighting performance, security, and ideal use‑cases for microservices.
This guide explains how to switch the embedded web server in Spring Boot 3.2.5, disable it, customize ports (including random and range ports), enable HTTP compression, configure SSL and HTTP/2, add servlets, filters, listeners, set up logging, and fine‑tune Tomcat and Undertow settings, all with practical code examples.
Apache Tomcat 10.1.10 has been released, bringing Jakarta EE 10 support, automatic migration of Java EE apps via the Jakarta EE Migration Tool, and notable updates such as virtual thread support, RFC‑9218 HTTP/2 priority, deprecation of xssProtectionEnabled, and an upgraded Tomcat Native 2.0.4 with OpenSSL 3.0.9.
cURL 8.1 introduces three main changes: support for HTTP/2 over HTTPS proxies via the –proxy-http2 option, rejection of hostnames ending with .onion during DNS resolution, and an expanded set of variables for the -w option to output URL components.
The article traces the evolution of Taobao’s unified mobile network library AWCN, detailing its MobileSDN architecture across north‑bound and south‑bound layers, key techniques such as IP‑list scheduling, adaptive protocol selection, multi‑path request handling and vendor acceleration, the challenges faced, performance gains observed during high‑traffic events, and future plans for finer network sensing and intelligent scheduling.
The article explains how modern browsers handle TCP connections and HTTP requests, covering persistent connections, the limits of HTTP/1.1 pipelining, the advantages of HTTP/2 multiplexing, and browser-imposed limits on simultaneous connections per host.
The curl 7.88.1 update addresses several critical bugs—including HTTP/2 multiplexed data corruption, inaccurate connection timeout handling, uninitialized port values in runtests, missing SRP support checks, HTTP3 fallback when HTTP2 is unavailable, and socketpair EWOULDBLOCK handling—enhancing reliability across platforms.
This article shares Tubi’s experience using Elixir‑gRPC in production, covering performance optimizations, stability measures, HTTP/2 edge‑case handling, and practical code examples for efficient Protobuf processing; it also discusses Envoy sidecar integration, interceptor usage, and lessons learned from real‑world deployments.
This article explains the key features of HTTP/2—including binary framing, header compression, flow control, multiplexing, request priority, and server push—alongside TLS 1.3 enhancements, ECC advantages, and Brotli compression, and provides practical Nginx configuration steps to leverage all of them for faster, more secure web delivery.
This article explains why reducing Nginx HTTPS latency is crucial for instant‑search services, describes how TLS handshakes add round‑trips, and provides concrete Nginx configuration tweaks—including enabling HTTP/2, optimizing cipher suites, activating OCSP stapling, adjusting ssl_buffer_size and SSL session cache—that together cut end‑to‑end request latency by roughly 30%.
This article introduces gRPC, explains its HTTP/2 and Protocol Buffers foundations, walks through writing and compiling .proto files, provides complete Python server and client examples, and shows how to quickly set up the environment and integrate gRPC into microservice and Kubernetes deployments.
To prevent massive user loss from slow loads, iQIYI International overhauled its mobile app’s network stack—switching to HTTPDNS, enabling TCP Fast Open, upgrading to HTTP/2 and TLS 1.3, compressing payloads with Brotli and WebP, using protobuf, caching, and fallback protocols—cut latency, reduced failures, and boosted video playback across Southeast Asian markets.
This article introduces the high‑performance gRPC framework, explains why it uses HTTP/2 and Protocol Buffers, outlines its core components, and provides a step‑by‑step Python tutorial with environment setup, code generation, server and client implementations, and common application scenarios.
This article explains the historical development of the HTTP protocol—from the simple HTTP/0.9 version through HTTP/1.0, 1.1, the binary‑based HTTP/2, and the emerging HTTP/3—highlighting each version's features, limitations, and the motivations behind their upgrades.
HTTP/2, now widely supported by browsers and major sites, replaces HTTP/1.1 by introducing a binary framing layer, header compression, stream prioritization, server push, and flow control, addressing head-of-line blocking and inefficiencies while maintaining HTTP semantics, with detailed discussion of its evolution, structure, and deployment considerations.
This article explains practical Nginx configuration tweaks—including enabling gzip compression, setting cache headers, activating HTTP/2, optimizing logging, and limiting bandwidth—to reduce bandwidth usage and server load, illustrated with code examples and performance impact calculations for typical web traffic.