Ideal Home Network Setup Diagram: Round Robin Load Balancer

Tech architecture infographic titled "Load Balancer Round Robin" using PROTOCOL HANDSHAKE (numbered exchanges). Show a minimal flat tech diagram for architect / staff audience, focused on how round-robin load balancing distributes sequential client requests across backend instances. Compose a clean left-to-right layout with labeled boxes and directional arrows. Include these boxes: 1) Browser — icon: web browser; name: "Browser"; role: "Client sending HTTPS requests". 2) Load Balancer — icon: traffic distributor / generic cloud gateway; name: "Load Balancer"; role: "Distributes requests across healthy servers". 3) API Server A — icon: application server; name: "API Server A"; role: "Processes REST requests". 4) API Server B — icon: application server; name: "API Server B"; role: "Processes REST requests". 5) API Server C — icon: application server; name: "API Server C"; role: "Processes REST requests". 6) Cache — icon: memory / lightning database; name: "Cache"; role: "Stores hot session or query data". 7) Queue — icon: message queue; name: "Queue"; role: "Buffers async jobs". 8) Database — icon: cylinder database; name: "Database"; role: "Persists application records". Connect all boxes with arrows showing accurate traffic direction: Browser to Load Balancer labeled "HTTPS request"; Load Balancer to API Server A labeled "Request 1 via TCP"; Load Balancer to API Server B labeled "Request 2 via TCP"; Load Balancer to API Server C labeled "Request 3 via TCP"; API servers back to Load Balancer labeled "HTTP 200 JSON"; Load Balancer back to Browser labeled "HTTPS response"; each API server to Cache labeled "GET / SET cache key"; each API server to Queue labeled "Publish job"; each API server to Database labeled "SELECT / INSERT / UPDATE"; Database back to API servers labeled "Row data / ack"; Queue to worker-style implied processing arrow labeled "Async task message" if space allows, otherwise keep queue passive. Emphasize round-robin sequencing with numbered exchanges near arrows: 1, 2, 3, 4, 5, 6, 7 showing consecutive requests rotating A then B then C then back to A conceptually. Add a small scheduler note near the load balancer: "Algorithm: Round Robin" and a neutral operational note: "Illustrative traffic distribution example, not an audited reference architecture". Add a numbered legend (1-7) in English: 1. "Browser opens HTTPS connection to the load balancer." 2. "Load balancer forwards the first request to API Server A." 3. "Next client request is forwarded to API Server B." 4. "Third client request is forwarded to API Server C." 5. "Each API server reads cache first, then queries the database if needed." 6. "Servers may publish asynchronous work to the queue before responding." 7. "Responses return through the load balancer to the browser with HTTP 200 when successful." Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use minimal flat shapes, crisp thin lines, subtle grid alignment, plenty of whitespace, calm expert mood, developer pink & teal palette with white or soft gray background, teal for transport paths, pink for balancing emphasis, muted violet accents for data services, gentle shadows only, no photorealism. Include generic cloud icons only, no vendor branding. 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).