Different Types of Network Topologies With Diagrams: Round Robin

Tech architecture infographic titled "Load Balancer Round Robin" using archetype REQUEST FLOW (client → server → DB). Show a beginner-friendly network request distribution diagram that explains how a round-robin load balancer forwards consecutive client requests evenly across multiple backend servers. Render a clean left-to-right layout with labeled boxes connected by directional arrows. Include these boxes: 1) Browser — icon: desktop monitor — role: "Sends HTTPS requests from the user". 2) Generic Cloud / Internet — icon: cloud — role: "Carries inbound network traffic". 3) Load Balancer — icon: network switch or traffic router — role: "Distributes requests across servers in round-robin order". 4) API Server A — icon: server rack — role: "Handles request and returns application response". 5) API Server B — icon: server rack — role: "Handles request and returns application response". 6) API Server C — icon: server rack — role: "Handles request and returns application response". 7) Cache — icon: memory chip — role: "Stores hot data for faster reads". 8) Queue — icon: stacked messages — role: "Buffers asynchronous jobs". 9) Database — icon: cylinder — role: "Persists application data". Connect with arrows showing accurate flow: Browser to Generic Cloud labeled "HTTPS request"; Generic Cloud to Load Balancer labeled "TCP connection / HTTPS"; Load Balancer to API Server A labeled "Request 1"; Load Balancer to API Server B labeled "Request 2"; Load Balancer to API Server C labeled "Request 3"; add looping sequence indicators so the next request returns to API Server A labeled "Round-robin cycle". From each API server to Cache label "Cache GET / SET"; from each API server to Queue label "Enqueue job"; from each API server to Database label "SELECT / INSERT / UPDATE"; return arrows from Cache, Queue acknowledgement path if shown, and Database back to API servers labeled "Data rows"; API servers back to Load Balancer labeled "HTTP 200 JSON response"; Load Balancer back to Browser labeled "HTTPS response". Include a small note near the load balancer: "Scheduling method: round robin, not load-aware". Add a numbered legend 1-7 in English: 1. "Browser opens an HTTPS request to the application endpoint." 2. "Traffic reaches the load balancer through the network." 3. "The load balancer sends request 1 to Server A." 4. "The next requests go to Server B, then Server C, then repeat." 5. "Each API server may read from cache and query the database." 6. "Long-running work can be pushed to a queue for async processing." 7. "The selected server returns an HTTP 200 response through the load balancer to the browser." Add subtle educational callouts for beginners: "Even distribution by request order", "Useful when backend servers are similar", "Does not check real-time server load by itself". Visual style: retro 1980s computing, blueprint cyan palette, dark cyan background with bright cyan linework, grid paper texture, CRT terminal accents, neon vector outlines, minimal off-white highlight text, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: nostalgic, technical, approachable, schematic, explanatory. Avoid any claim that this is an audited or production-certified reference architecture. No real cloud-vendor logos; use only generic cloud and server icons. 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).