Precedence Network in Software Project Management Infographic

Tech architecture infographic titled "Redis Cache Invalidation" using archetype DATA PIPELINE (extract → transform → load), adapted to explain cache invalidation lifecycle for a curious beginner. Show a clean left-to-right pipeline with labeled boxes and arrows: Browser, API Service, Redis Cache, Message Queue, Worker, Primary Database, plus an optional Monitoring box. Each box must contain a simple icon, a canonical English name, and a one-line English role description. Required boxes: Browser — icon: web window — role: "Sends read and write requests"; API Service — icon: server rack — role: "Handles REST requests and business logic"; Redis Cache — icon: layered memory cylinder — role: "Stores hot key-value data for fast reads"; Message Queue — icon: queue or stacked messages — role: "Buffers invalidation events asynchronously"; Worker — icon: gear or bot — role: "Consumes events and deletes or refreshes cache keys"; Primary Database — icon: database cylinder — role: "Source of truth for persistent records"; Monitoring — icon: chart pulse — role: "Tracks cache hit rate and invalidation lag". Use arrows with short English labels showing exact data movement and protocol-aware terms: Browser → API Service labeled "HTTPS GET /item/42"; API Service → Redis Cache labeled "GET cache:key:42"; Redis Cache → API Service labeled "Cache hit: JSON value"; API Service → Primary Database labeled "SELECT row"; Primary Database → API Service labeled "Row data"; API Service → Redis Cache labeled "SETEX cache:key:42 TTL 300s"; Browser → API Service labeled "HTTPS PUT /item/42"; API Service → Primary Database labeled "UPDATE row"; API Service → Message Queue labeled "Publish invalidation event"; Message Queue → Worker labeled "Cache key event"; Worker → Redis Cache labeled "DEL cache:key:42"; optional Worker → Redis Cache labeled "SET refreshed JSON"; API Service → Browser labeled "200 OK JSON response". Visually separate read path and write path: read path in cyan arrows, write and invalidation path in darker blue arrows, with a highlighted note that invalidation happens after successful database update. Add small callout labels such as "Cache miss", "Cache hit", "Stale data risk", and "TTL fallback" in English. Include a numbered legend 1-7 in English walking through the lifecycle: 1. "Browser sends an HTTPS read request to the API" 2. "API checks Redis for cache:key:42" 3. "On cache miss, API reads the record from the primary database" 4. "API stores the fresh result in Redis with TTL and returns 200 OK JSON" 5. "A write request updates the database source of truth" 6. "API publishes an invalidation event to the queue after the update succeeds" 7. "Worker deletes or refreshes the Redis key so later reads do not serve stale data". Add a small beginner-friendly caution note in English: "Illustrative pattern, not an audited reference architecture". Visual style: hand-drawn whiteboard, cool blue and cyan palette, sketchy marker outlines, soft grid background, friendly educational tone, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Keep composition uncluttered, high readability, simple icons, generous spacing, and clear directional flow. Do not include any real cloud-vendor logos; if cloud is shown, use only generic cloud 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).