Diagrama lan de flujo de solicitudes CDN en modo oscuro

Tech architecture infographic titled "CDN Request Flow" — HOW-IT-WORKS archetype, designed for a curious beginner. Show a clear numbered flow with labeled boxes connected by directional arrows, explaining how a CDN serves web content. Include these main components as vector boxes with icons, canonical English names, and one-line English role descriptions: 1) Browser — 'User client requesting a web page or asset'; 2) DNS Resolver — 'Translates domain name to the nearest CDN endpoint'; 3) CDN Edge Server — 'Caches and serves content close to the user'; 4) Cache Layer — 'Stores recently requested assets for fast delivery'; 5) Origin Load Balancer — 'Routes cache-miss traffic to the correct backend'; 6) Origin API / Web Server — 'Generates dynamic responses or returns source files'; 7) Database — 'Stores application data for dynamic content'; 8) Message Queue — 'Handles asynchronous background jobs when needed'. Use arrows with short English labels showing technically accurate data movement: Browser → DNS Resolver 'DNS query'; DNS Resolver → Browser 'CDN edge IP'; Browser → CDN Edge Server 'HTTPS GET /asset'; CDN Edge Server → Cache Layer 'Cache lookup'; Cache Layer → CDN Edge Server 'Cache hit: file'; CDN Edge Server → Browser 'HTTP 200 OK + cached asset'; for cache miss path: Cache Layer → CDN Edge Server 'Cache miss'; CDN Edge Server → Origin Load Balancer 'HTTPS origin fetch'; Origin Load Balancer → Origin API / Web Server 'Forward request'; Origin API / Web Server → Database 'SQL query'; Database → Origin API / Web Server 'Rows / result'; Origin API / Web Server → Message Queue 'Async job event'; Message Queue → Origin API / Web Server 'Job ack'; Origin API / Web Server → Origin Load Balancer 'HTTP 200 OK + origin content'; Origin Load Balancer → CDN Edge Server 'Origin response'; CDN Edge Server → Cache Layer 'Store asset with TTL'; CDN Edge Server → Browser 'HTTP 200 OK + content'. Add small optional callouts for 'Static asset', 'Dynamic content', 'TTL', 'Cache hit', and 'Cache miss'. Include a numbered legend 1-7 in English walking through the lifecycle: 1. Browser requests a page or asset over HTTPS. 2. DNS sends the user to a nearby CDN edge location. 3. The CDN checks whether the requested content is already cached. 4. On a cache hit, the edge returns the asset immediately with HTTP 200 OK. 5. On a cache miss, the edge fetches the content from the origin through the load balancer. 6. The origin server may query the database or trigger asynchronous work before responding. 7. The CDN stores the fresh content in cache and delivers it to the browser for faster future requests. Make the composition easy to scan, with the main happy path emphasized and the cache-miss path as a secondary branch. Style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Visual mood: dark-mode developer, sleek, approachable, educational, modern neon glow. Color palette: charcoal and near-black background, neon cyan, electric blue, violet, magenta, and lime accents, with high-contrast white English labels. Use subtle grid, soft glows, clean spacing, rounded boxes, thin luminous arrows, and beginner-friendly hierarchy. Include generic cloud and network icons only, no real cloud-vendor branding, and avoid implying this is an audited reference architecture. 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).