Cisco Topology Software CDN Request Flow Infographic

Tech architecture infographic titled "CDN Request Flow" using archetype REQUEST FLOW (client → server → cache/storage). Show a clear left-to-right flow for a curious beginner. Render labeled boxes with icons, names, and one-line role descriptions in English: 1) Browser — icon: web browser — role: "User client requesting a web page or asset"; 2) DNS Resolver — icon: globe/network — role: "Finds the CDN edge address for the domain"; 3) CDN Edge Server — icon: cloud + lightning — role: "Serves cached content from the nearest edge location"; 4) Load Balancer / Reverse Proxy — icon: traffic router — role: "Forwards cache misses to the origin service"; 5) Origin API / Web Server — icon: server rack — role: "Generates content or returns the requested file"; 6) Cache Layer — icon: memory chip — role: "Stores frequently requested responses for faster delivery"; 7) Database — icon: cylinder — role: "Persists application data used by the origin"; 8) Background Queue — icon: queue stack — role: "Handles async jobs such as image resize or cache purge". Connect all boxes with directional arrows and short English labels showing what crosses: Browser → DNS Resolver: "DNS query"; DNS Resolver → Browser: "CDN edge IP"; Browser → CDN Edge Server: "HTTPS GET /asset"; CDN Edge Server → Browser: "200 OK cached asset"; CDN Edge Server → Load Balancer / Reverse Proxy: "Cache miss over HTTPS"; Load Balancer / Reverse Proxy → Origin API / Web Server: "Forwarded HTTP request"; Origin API / Web Server → Cache Layer: "Read / write cache"; Cache Layer → Origin API / Web Server: "Cached object or miss"; Origin API / Web Server → Database: "SELECT / INSERT row"; Database → Origin API / Web Server: "Query result"; Origin API / Web Server → Background Queue: "Purge job / image resize task"; Origin API / Web Server → CDN Edge Server: "200 OK origin response"; CDN Edge Server → Browser: "200 OK asset from edge". Include optional small callouts for cache behavior: "Cache hit", "Cache miss", "TTL expires", "Revalidation with ETag / If-None-Match", and a subtle note that CDN content may be static assets, HTML, API responses, or media files. Add a numbered legend 1-7 in English walking through the lifecycle: 1. "Browser requests a page or asset over HTTPS." 2. "DNS resolves the domain to a nearby CDN edge server." 3. "CDN edge checks whether the object is already cached." 4. "If cache hit, the edge returns 200 OK immediately." 5. "If cache miss, the edge forwards the request to the origin through the reverse proxy." 6. "Origin reads cache and database data, builds the response, and may enqueue async jobs." 7. "CDN stores the fresh response according to TTL and delivers it back to the browser faster on future requests." Add small beginner-friendly metrics/callouts in English such as "Lower latency", "Reduced origin load", "Cache hit ratio", and "TTL". Visual style: cyberpunk neon with warm beige & navy palette, glowing edge highlights, subtle grid background, luminous arrows, high contrast labels, futuristic but readable, approachable educational mood, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Avoid any audited or compliance-style claims; present it as an educational conceptual diagram only. 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).