HTTP/2 Multiplexing Network Figure for System Architects

Tech architecture infographic titled "HTTP/2 Multiplexing" using archetype PROTOCOL HANDSHAKE, designed for architect / staff audience. Show a precise network figure explaining how HTTP/2 multiplexing works over a single connection. Layout: left-to-right technical sequence with labeled boxes and directional arrows, plus a lower numbered legend. Include these boxes: 1) Browser — icon: desktop browser window — role: "Client opens one HTTP/2 connection and sends parallel streams". 2) DNS Resolver — icon: network node — role: "Resolves origin host to IP address". 3) TLS Terminator / Web Server — icon: rack server with lock — role: "Negotiates TLS and HTTP/2 session settings". 4) Stream Scheduler — icon: branching lanes — role: "Interleaves frames from multiple request streams on one TCP connection". 5) API Service — icon: service cube — role: "Processes REST or GraphQL application requests". 6) Cache — icon: memory chip — role: "Serves reusable responses with low latency". 7) Queue — icon: message queue stack — role: "Buffers asynchronous jobs triggered by requests". 8) Database — icon: cylinder — role: "Stores persistent application data". 9) Generic Cloud Edge — icon: generic cloud — role: "Represents public network path without vendor branding". Connect boxes with arrows showing accurate protocol flow and multiplexing behavior. Arrows must be labeled in English with short precise captions such as: "DNS query", "A / AAAA record", "TCP 3-way handshake", "TLS handshake + ALPN h2", "HTTP/2 SETTINGS", "HEADERS stream 1", "HEADERS stream 3", "DATA frames interleaved", "REST JSON request", "GraphQL query", "Cache hit", "Cache miss", "SELECT rows", "INSERT row", "Job message", "JSON response", "HTTP 200", "HTTP 304". Depict one single TCP connection between Browser and TLS Terminator / Web Server, with multiple colored logical streams inside it, clearly numbered stream 1, stream 3, stream 5, showing interleaved HEADERS and DATA frames returning out of order while preserving per-stream assembly. Include a small callout note box: "Multiplexing reduces head-of-line blocking at the HTTP layer, but TCP loss still blocks all streams on that connection". Include another small callout note box: "Server Push was defined in HTTP/2 but is rarely used in modern browsers". Show backend fan-out from Web Server / API Service to Cache, Queue, and Database as secondary request paths. Add a numbered legend 1-7 in English walking through the lifecycle: 1. "Browser resolves the origin and opens a TCP connection." 2. "TLS negotiates HTTP/2 via ALPN using h2." 3. "Client and server exchange SETTINGS frames and establish stream rules." 4. "Browser sends multiple requests concurrently as separate streams on one connection." 5. "Server interleaves HEADERS and DATA frames from different streams based on priority and availability." 6. "Application reads or writes cache, queue, and database as needed, then emits per-stream responses." 7. "Browser reassembles frames by stream ID and renders each response independently." Visual style: retro 1980s computing, blueprint cyan palette, dark navy background with cyan linework, grid paper texture, glowing vector strokes, monochrome cyan plus subtle white highlights, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, crisp technical annotations, staff-level systems thinking, clean spacing, no vendor branding, no exaggerated security claims, not an audited reference architecture. 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).