Load Balancer Round Robin Infographic for Network Diagramming Products

Tech architecture infographic titled "Load Balancer Round Robin" using PROTOCOL HANDSHAKE (numbered exchanges). Show a beginner-friendly flat network diagram that explains how round-robin load balancing distributes incoming requests across multiple backend servers in sequence. Layout with clearly labeled boxes connected by directional arrows: Client Browser, DNS Resolver, Load Balancer, API Server A, API Server B, API Server C, Cache, Queue, Database, and Generic Cloud Network. Each box must include a simple icon, a canonical English component name, and a one-line English role description. Example role descriptions: Browser — "Sends HTTPS requests from the user"; Load Balancer — "Distributes requests evenly across servers"; API Server A — "Processes request and returns REST response"; Cache — "Stores hot data for faster reads"; Queue — "Buffers asynchronous background jobs"; Database — "Persists application records". Use numbered exchange arrows to depict an accurate flow: 1) Browser to DNS Resolver labeled "DNS query"; 2) DNS Resolver to Browser labeled "IP address response"; 3) Browser to Load Balancer labeled "TCP handshake + HTTPS request"; 4) Load Balancer to API Server A labeled "Round robin: request 1"; 5) Browser next request to Load Balancer labeled "HTTPS request 2"; 6) Load Balancer to API Server B labeled "Round robin: request 2"; 7) Browser next request to Load Balancer labeled "HTTPS request 3"; 8) Load Balancer to API Server C labeled "Round robin: request 3". Show backend service interactions where appropriate: API servers to Cache labeled "GET cached value" / "SET cached value"; API servers to Database labeled "SELECT row" / "INSERT row"; API servers to Queue labeled "Publish job"; return arrows from API servers back through Load Balancer to Browser labeled "HTTP 200 JSON response". Make clear that the load balancer rotates requests sequentially A → B → C → A, not based on session affinity. Include a small note box in English: "Illustrative example, not an audited reference architecture." Add a numbered legend 1-7 in English walking through the lifecycle: 1. User request begins in the browser. 2. DNS resolves the service address. 3. Browser opens TCP and sends HTTPS to the load balancer. 4. Load balancer forwards the first request to API Server A. 5. The next incoming request is forwarded to API Server B. 6. The third incoming request is forwarded to API Server C. 7. Each server may read cache, update database, enqueue work, and return an HTTP 200 JSON response through the load balancer. Visual style: minimal flat, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a developer pink & teal palette with soft neutral background, thin dark outlines, subtle shadows, rounded rectangles, crisp arrows, clean spacing, approachable beginner-friendly mood, modern diagram aesthetics, 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).