HTTP/2 Multiplexing Vertical Swimlane Diagram

Tech architecture infographic titled "HTTP/2 Multiplexing" — archetype: PROTOCOL HANDSHAKE shown as a vertical swimlane diagram for architect / staff audience. Depict a technically accurate HTTP/2 connection flow with labeled boxes and directional arrows, using stacked vertical swimlanes for Client, Network Edge, Application Server, Cache, Queue, and Database. Show a single persistent connection carrying multiple concurrent streams. Include these labeled boxes with icon + canonical English name + one-line English role description: 1) Browser — "User agent initiating HTTPS requests over one connection"; 2) DNS / CDN Edge — "Resolves host and forwards traffic to origin"; 3) TLS Terminator / HTTP/2 Gateway — "Negotiates ALPN h2 and manages framed streams"; 4) API Server — "Processes requests and generates responses"; 5) Cache — "Serves hot objects with low-latency lookup"; 6) Queue — "Buffers async work outside request path"; 7) Database — "Stores durable application records". Render arrows between boxes with short English labels describing exchanged data: "DNS query", "A / AAAA record", "TCP 3-way handshake", "TLS 1.2+ handshake", "ALPN: h2", "HTTP/2 SETTINGS", "HEADERS stream 1", "HEADERS stream 3", "DATA frames", "REST JSON request", "Cache GET", "Cache HIT", "Enqueue job", "SQL SELECT", "SQL result", "JSON response", "DATA frames interleaved", "HTTP 200". Visually emphasize HTTP/2 multiplexing: multiple request streams (for example stream 1 HTML, stream 3 CSS, stream 5 JS, stream 7 image, stream 9 API call) sharing one HTTPS/TCP connection, with interleaved colored frame segments, stream IDs, bidirectional arrows, and no head-of-line blocking at the HTTP message layer. Include numbered exchanges and lifecycle callouts: 1) Browser resolves origin and opens one TCP connection. 2) TLS handshake negotiates HTTPS with ALPN selecting HTTP/2. 3) Client and server exchange SETTINGS frames and establish stream-based communication. 4) Browser sends multiple HEADERS frames for parallel resources on separate stream IDs. 5) Server routes work to API, cache, queue, and database as needed per request. 6) Response HEADERS and DATA frames for different streams are interleaved over the same connection. 7) Browser reassembles frames by stream ID and renders resources as they complete. Add a numbered legend (1-7) in English repeating this lifecycle succinctly. Include subtle metrics / annotations in English such as "1 connection", "N concurrent streams", "binary framing", "header compression (HPACK)", "server push optional / legacy note". Make clear this is an explanatory architecture diagram, not an audited reference architecture. Visual style: retro 1980s computing, blueprint cyan palette, luminous cyan lines on dark navy blueprint background, CRT terminal vibe, grid paper, wireframe icons, neon edge highlights, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. 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).