dmn diagram for Redis Cache Invalidation Request Flow

Tech architecture infographic titled "Redis Cache Invalidation" using REQUEST FLOW archetype. Show a beginner-friendly client-to-server request flow with labeled boxes connected by directional arrows: Browser, API Server, Redis Cache, Primary Database, Message Queue, and optional Worker/Invalidation Consumer. Each box must include a simple icon, the component name in canonical English-tech form, and a one-line English role description: Browser — "User app sending HTTPS requests"; API Server — "Handles REST requests and cache logic"; Redis Cache — "Stores hot key-value data for fast reads"; Primary Database — "Source of truth for persistent records"; Message Queue — "Buffers invalidation events asynchronously"; Worker — "Consumes events and deletes stale cache keys". Show clear arrows with short English labels: Browser to API Server "HTTPS GET /item/42"; API Server to Redis Cache "GET cache:item:42"; Redis Cache to API Server "cache hit: JSON" or "cache miss"; API Server to Primary Database "SELECT row"; Primary Database to API Server "row data"; API Server to Redis Cache "SET cache:item:42 TTL 300s"; API Server to Browser "200 OK JSON response"; Browser to API Server "HTTPS PUT /item/42"; API Server to Primary Database "UPDATE row"; Primary Database to API Server "200 OK / rows affected"; API Server to Message Queue "publish invalidation event"; Message Queue to Worker "cache key event"; Worker to Redis Cache "DEL cache:item:42"; optional direct API Server to Redis Cache arrow "DEL cache:item:42" for synchronous invalidation. Visually distinguish read path versus write path and emphasize cache invalidation after data mutation so stale data is removed before next read. Add a numbered legend 1-7 in English explaining lifecycle: 1. Browser sends HTTPS read request to API. 2. API checks Redis for cached object. 3. On cache miss, API reads from Database and returns 200 OK. 4. API stores fresh result in Redis with TTL. 5. Browser sends update request that changes the record. 6. API updates Database and triggers cache invalidation via DEL or queue event. 7. Next read misses cache, reloads fresh data, and repopulates Redis. Include tiny side note labels such as "Read path", "Write path", "Cache hit", "Cache miss", "TTL expiry", and "Stale entry removed". Make the flow technically accurate for Redis cache invalidation in a REST API context, clearly showing that Database is the source of truth and Redis is a performance layer, not authoritative storage. Style: cyberpunk neon mixed with warm beige and navy palette, glowing accent lines, dark navy background, warm beige panels, magenta/cyan neon highlights, high contrast but readable typography, soft grid, subtle futuristic UI framing. Overall mood: modern, energetic, educational, approachable for curious beginners, not an audited reference architecture. editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. 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).