Network Primitives.
Exposed.
No abstractions. We analyze the raw TCP/IP stack, routing topologies, and binary frames that govern web architecture.
State of the Web Stack (2024)
QUIC protocol dominating high-latency mobile networks.
Down from 2 RTTs in TLS 1.2, saving ~50-100ms per connection.
Global routing table size, increasing memory demands on edge routers.
The absolute limit before IP fragmentation occurs on the WAN.
The Cost of Abstraction
Frameworks hide latency. Cloud providers hide topology. But the laws of physics and network routing remain absolute. A millisecond lost in a bloated TCP handshake is a millisecond you cannot buy back.
We dissect the wire. From BGP convergence times to exactly how HTTP/3 leverages UDP multiplexing to defeat head-of-line blocking.
Understanding these primitives is the difference between a resilient architecture and one that collapses under high latency or packet loss.
Explore Architecture GuidelinesLatency is dictated by the speed of light in fiber.
~200,000 km/second.
Everything else is queueing delay, processing delay, or protocol overhead.
Architectural Patterns
Anycast Routing
Deploying the same IP address across multiple geographic locations. BGP routes the client to the topologically closest edge node, minimizing TCP handshake duration.
Read Analysis →Connection Pooling
Reusing established TCP/TLS connections to avoid the 3-RTT penalty on subsequent requests. Essential for microservice-to-database communication.
Read Analysis →Early Hints (103)
Emitting Link headers before the main HTML payload is fully generated, allowing the browser to begin DNS resolution and TCP handshakes for critical assets.
Read Analysis →Network Calculators
Client-side tools for immediate architectural math. No tracking, no backend calls.
Subnet CIDR Calculator
Calculate network boundaries, usable hosts, and broadcast addresses instantly.
Launch Tool →TCP Window Size Math
Determine maximum theoretical throughput given a specific latency and window size.
Launch Tool →DNS Propagation Checker
Simulate TTL expiration and global record propagation timelines.
Launch Tool →Observation 01: The death of TCP on the edge.
With HTTP/3 (QUIC) operating over UDP, the long-standing dominance of TCP for web traffic is ending at the client-edge boundary. TCP remains entrenched in data center backbones, but the mobile web has moved to UDP to defeat head-of-line blocking.
Observation 02: Encryption is no longer optional.
Browsers now enforce TLS for basic API features. The performance penalty of TLS handshakes has been heavily mitigated by TLS 1.3 and 0-RTT resumption, leaving no architectural excuse for plaintext transit.
Core Concepts FAQ
Why does DNS over HTTPS (DoH) matter?
Standard DNS traverses port 53 in plaintext, allowing ISPs and intermediate nodes to monitor or hijack queries. DoH encapsulates the resolution within a standard HTTPS stream (port 443), securing the SNI payload and preventing local network tampering.
What is Head-of-Line Blocking?
In HTTP/2 over TCP, if a single packet is dropped, the entire stream halts waiting for retransmission. HTTP/3 fixes this by moving to QUIC (UDP), where independent byte streams don't block each other if one drops a packet.
How large is an MTU realistically?
While Jumbo Frames support 9000 bytes within local data centers, the global internet backbone enforces a strict Maximum Transmission Unit (MTU) of 1500 bytes. Subtracting 20 bytes for IP and 20 for TCP leaves 1460 bytes for payload (MSS).
What is BGP Hijacking?
Because BGP historically lacked cryptographic verification, a malicious AS could announce a shorter path to a target IP block, blackholing or intercepting traffic. RPKI (Resource Public Key Infrastructure) is slowly mitigating this by validating route origins.