networkdiagram101 CDN Request Flow Tech Infographic

Tech architecture infographic titled "CDN Request Flow" using archetype HOW-IT-WORKS with lifecycle/state-machine progression for a non-technical executive audience. Show a clean left-to-right blueprint schematic of labeled boxes connected by directional arrows, explaining how a CDN serves content. Include these boxes with icons, canonical English names, and one-line English role descriptions: 1) Browser — "End-user client requesting a web asset"; 2) DNS Resolver — "Finds the CDN edge endpoint for the domain"; 3) CDN Edge Cache — "Nearest edge server that serves cached content"; 4) CDN Request Router — "Selects edge behavior and forwards cache misses"; 5) Origin Load Balancer — "Distributes origin fetches across backend servers"; 6) Origin Web Server / API — "Primary source that generates or returns content"; 7) Object Storage / Database — "Persistent storage for files and application data"; 8) Cache Invalidation Queue — "Propagates purge and refresh events across edges"; 9) Monitoring / Logs — "Collects request metrics, cache status, and errors". Use arrows with short English labels showing technically accurate flow: Browser to DNS Resolver "DNS query"; DNS Resolver to Browser "CDN edge IP"; Browser to CDN Edge Cache "HTTPS GET /asset"; CDN Edge Cache to Browser "200 OK cached response"; CDN Edge Cache to CDN Request Router "Cache miss metadata"; CDN Request Router to Origin Load Balancer "Origin fetch over HTTPS"; Origin Load Balancer to Origin Web Server / API "Forward request"; Origin Web Server / API to Object Storage / Database "Read file / query data"; Object Storage / Database to Origin Web Server / API "Content / records"; Origin Web Server / API to Origin Load Balancer "200 OK origin response"; Origin Load Balancer to CDN Request Router "Origin payload"; CDN Request Router to CDN Edge Cache "Store with Cache-Control / ETag"; CDN Edge Cache to Browser "200 OK edge response"; Cache Invalidation Queue to CDN Edge Cache "PURGE / invalidate"; CDN Edge Cache to Monitoring / Logs "Hit / miss / latency logs". Visually distinguish states in the lifecycle with subtle numbered stage markers and a state-flow rhythm: Request Start, Name Resolution, Edge Check, Cache Hit path, Cache Miss path, Origin Fetch, Edge Fill, Response Delivery, Invalidation and Observability. Add a numbered legend 1-7 in English: 1. "Browser requests a static asset over HTTPS." 2. "DNS resolves the domain to the nearest CDN edge location." 3. "The CDN edge checks whether the asset is already cached." 4. "If cached, the edge returns a 200 OK response immediately." 5. "If not cached, the CDN forwards an origin fetch to the backend." 6. "The origin server reads content from storage or data systems and returns it." 7. "The edge stores the response according to Cache-Control or ETag rules, then serves the user and records logs." Include small executive-friendly callouts such as "Lower latency on cache hit" and "Origin load reduced by edge caching" without making security or audit claims. Style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, blueprint schematic, minimal monochrome palette, dark navy background with white and light gray linework, subtle grid, crisp thin strokes, restrained highlights, calm technical mood, simple icons, spacious composition, easy-to-scan hierarchy, 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).