HTTP/2 Multiplexing WAN Diagram Tech Architecture Infographic

Tech architecture infographic titled "HTTP/2 Multiplexing" using PROTOCOL HANDSHAKE archetype with numbered exchanges. Show a minimal flat, senior-engineer-focused how-it-works diagram explaining how HTTP/2 multiplexing carries multiple concurrent request-response streams over one TCP connection. Layout left-to-right with labeled boxes and directional arrows: Browser — client app that opens one HTTPS connection and sends many logical streams; API Gateway / Web Server — HTTP/2 endpoint that terminates TLS and manages frames and stream scheduling; Cache — hot object store that serves reusable responses quickly; Queue — async work buffer for background processing; Application Service — request handler that routes business logic; Database — persistent data store for records and queries; Generic Cloud Network — public internet path between client and server using generic cloud icons only. Include clear icons in every box, canonical English-tech names, and one-line English role descriptions inside each box. Emphasize protocol layers visually: DNS lookup optional small side note, then TCP 3-way handshake, TLS handshake with ALPN negotiation for h2, then a single persistent HTTP/2 connection containing multiple colored parallel streams Stream 1, Stream 3, Stream 5, Stream 7 as multiplexed lanes. Depict HTTP/2 frame types accurately: HEADERS, DATA, SETTINGS, WINDOW_UPDATE, PING, GOAWAY. Show streams interleaved on the same connection rather than separate TCP sockets. Show server push only as optional muted note, not primary flow. Arrows must be labeled in English with technically accurate payloads such as: "DNS query", "TCP SYN", "SYN-ACK", "ACK", "TLS ClientHello + ALPN h2", "TLS ServerHello", "HTTP/2 SETTINGS", "HEADERS frame", "DATA frame", "JSON response", "Cache HIT", "Cache MISS", "SQL query", "Job message", "200 OK", "RST_STREAM", "GOAWAY". Make the main numbered exchange sequence explicit: 1 Browser resolves host and opens TCP connection to API endpoint, 2 TLS handshake negotiates HTTPS with ALPN selecting h2, 3 Client and server exchange HTTP/2 SETTINGS on one persistent connection, 4 Browser sends multiple concurrent request streams with interleaved HEADERS and DATA frames, 5 API server demultiplexes streams and routes work to Cache, Application Service, Queue, and Database as needed, 6 Responses from cache or backend are re-multiplexed into interleaved frames on the same connection with per-stream IDs and flow control, 7 Browser reconstructs each stream independently and renders resources as 200 OK responses complete. Include a numbered legend 1-7 in English walking through this lifecycle for senior engineers, mentioning stream IDs, prioritization as optional/deemphasized, head-of-line blocking avoided at HTTP layer but still possible at TCP layer, and connection reuse. Add a small comparison inset labeled "Without Multiplexing" showing several separate HTTP/1.1 request lanes versus one "Single HTTP/2 Connection" lane with many streams. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, minimal flat geometry, crisp outlines, subtle grid, generous whitespace, compact labels, elegant annotations, developer pink & teal palette with dark slate text, teal connection lanes, pink stream accents, soft gray containers, muted cloud/network background, modern technical mood. Include note that this is an explanatory architecture diagram, not an audited security reference. 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).