HTTP/2 Multiplexing Vertical Swimlane Diagram Infographic

Tech architecture infographic titled "HTTP/2 Multiplexing" using archetype PROTOCOL HANDSHAKE, presented as a vertical swimlane diagram for a non-technical executive audience. Show clear vertical lanes with labeled boxes and directional arrows explaining how multiple HTTP requests share one connection. Include these component boxes in canonical English-tech form: Browser — 'Client app requesting web resources'; CDN/Edge — 'Optional edge layer serving static assets'; API Gateway — 'Entry point terminating HTTPS and routing traffic'; App Server — 'Processes requests and builds responses'; Cache — 'Stores reusable responses or fragments'; Queue — 'Handles async background work when needed'; Database — 'Persists application data'; TCP Connection — 'Single transport connection carrying all streams'; HTTP/2 Stream 1 — 'Independent request-response channel'; HTTP/2 Stream 2 — 'Independent request-response channel'; HTTP/2 Stream 3 — 'Independent request-response channel'. Each box must have an icon, a name, and a one-line role description in English. Show arrows with short English labels describing what crosses: 'TLS handshake', 'HTTP/2 SETTINGS', 'HEADERS frame', 'DATA frame', 'Multiplexed streams', 'Cache lookup', 'Cache hit', 'SQL query', 'Result rows', 'Enqueue job', '202 Accepted', '200 OK HTML', '200 OK JSON', '200 OK CSS', '200 OK JS'. Depict technically accurate flow: Browser opens one HTTPS over TCP connection, negotiates HTTP/2 via ALPN during TLS handshake, sends multiple concurrent requests on separate HTTP/2 stream IDs over the same connection, frames are interleaved, server processes requests independently, responses return as multiplexed streams over the same connection. Visually contrast old HTTP/1.1 multiple parallel connections in a small side note versus HTTP/2 single shared connection with many streams, but keep the main focus on HTTP/2 multiplexing. Add subtle notes for exec clarity: 'One connection, many streams', 'Reduced connection overhead', 'Better page loading efficiency', avoiding any exaggerated security or performance claims. Include a numbered legend 1-7 in English: 1. Browser starts one TCP connection and TLS session to the server. 2. TLS negotiates HTTP/2 using ALPN. 3. Browser sends multiple requests concurrently as separate HTTP/2 streams. 4. HEADERS and DATA frames from different streams are interleaved on one connection. 5. Server routes each stream to app logic, cache, queue, or database as needed. 6. Server returns independent responses on the same shared connection with proper HTTP status codes such as 200 OK or 202 Accepted. 7. Browser reassembles frames by stream ID and renders assets as they arrive. Visual style: retro 1980s computing, blueprint cyan palette, glowing cyan lines on deep navy background, grid paper feel, vintage terminal-inspired icons, subtle scanline texture, crisp geometric arrows, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Keep composition clean, executive-friendly, and easy to scan, with labeled boxes for browser, API, DB, cache, and queue connected by arrows showing data direction. 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).