High Level Network Architecture Diagram for HTTP/2 Multiplexing

Tech architecture infographic titled "HTTP/2 Multiplexing" using archetype HOW-IT-WORKS (numbered stages). Show a high-level network architecture diagram focused on how HTTP/2 multiplexing works across a single client-server connection. Create labeled boxes connected by directional arrows in a clear left-to-right flow with numbered stages and a compact bottom legend for architect / staff audience. Include these boxes even if some are ancillary to the protocol path: 1) Browser — icon: web browser — role: 'Client opens one HTTP/2 connection and sends many concurrent requests'; 2) TLS Terminator / Edge Proxy — icon: shield plus network gateway — role: 'Negotiates ALPN and forwards HTTP/2 traffic upstream'; 3) API Server — icon: server rack — role: 'Processes multiplexed streams and returns responses independently'; 4) Cache — icon: lightning cache cylinder — role: 'Serves reusable content with low latency'; 5) Queue — icon: message queue — role: 'Buffers asynchronous work triggered by requests'; 6) Database — icon: database cylinder — role: 'Stores and retrieves persistent application data'. Show the main protocol path prominently: Browser to TLS Terminator / Edge Proxy to API Server over a single TCP connection carrying many HTTP/2 streams. Visually depict one connection line containing multiple colored sub-stream lanes with interleaved frames. From API Server branch to Cache, Queue, and Database with return arrows back to API Server. Optionally show a small generic cloud icon behind the server-side cluster, but no vendor branding. Put short arrow labels in English on every connector: Browser -> TLS Terminator label 'HTTPS + TLS ALPN h2'; TLS Terminator -> API Server label 'HTTP/2 frames over 1 TCP connection'; inside the main connection annotate stream examples 'Stream 1 GET /feed', 'Stream 3 GET /avatar', 'Stream 5 POST /event'; API Server -> Cache label 'cache lookup'; Cache -> API Server label 'cache hit / miss'; API Server -> Queue label 'enqueue job'; API Server -> Database label 'SELECT / INSERT'; API Server -> Browser label 'interleaved response frames'; add a small note near the connection 'multiplexed streams, no HTTP/1.1 head-of-line at application layer'. Add subtle technical callouts: 'binary framing', 'stream IDs', 'HPACK header compression', 'prioritization optional', 'flow control per stream and connection', 'server push legacy / rarely used' as side annotations, but keep them compact and accurate. Do not claim performance guarantees; present as explanatory architecture only. Numbered legend 1-7 in English: 1. 'Browser establishes TCP and TLS, negotiates h2 with ALPN.' 2. 'One HTTP/2 connection is reused for many requests to the same origin.' 3. 'Each request becomes a separate stream with its own stream ID.' 4. 'Frames from multiple streams are interleaved on the same connection.' 5. 'Edge proxy and API server route work to cache, queue, and database as needed.' 6. 'Responses return as HEADERS and DATA frames, interleaved independently by stream.' 7. 'Browser reassembles frames by stream ID and renders resources as they complete.' Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Dark-mode developer aesthetic, dark charcoal background, neon cyan, electric blue, violet, and magenta highlights, subtle grid, glowing arrows, crisp boxes, precise typography, high contrast, sophisticated staff-level technical mood. Compose for readability: title top, architecture center, side callouts for protocol mechanics, numbered legend bottom. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).