AWS Web Application Diagram: Event Sourcing Pattern

Tech architecture infographic titled "Event Sourcing Pattern" using archetype SYSTEM ARCHITECTURE (services + queues + storage). Show a mid-level-developer-friendly event sourcing web application diagram with labeled boxes connected by directional arrows, explaining how commands become immutable events, how state is rebuilt from the event log, and how read models are updated. Include these boxes: 1) Web Browser — icon: browser window — role: 'User interface sends commands and queries over HTTPS'; 2) API Gateway / REST API — icon: endpoint nodes — role: 'Validates requests and routes commands and queries'; 3) Command Handler Service — icon: gear or microservice chip — role: 'Applies business rules and creates domain events'; 4) Event Store Database — icon: append-only database cylinder — role: 'Stores immutable ordered event stream by aggregate'; 5) Message Queue / Event Bus — icon: queue or bus — role: 'Publishes committed events to subscribers asynchronously'; 6) Projection Worker — icon: worker gear — role: 'Builds read models from event stream updates'; 7) Read Model Database — icon: query database cylinder — role: 'Serves denormalized views optimized for reads'; 8) Cache — icon: lightning cache box — role: 'Accelerates frequent query responses'; 9) Query API — icon: magnifier plus endpoint — role: 'Fetches read-optimized data for the UI'; 10) Monitoring / Audit Log — icon: terminal or log sheet — role: 'Tracks event processing and system health'; 11) Generic Cloud Boundary — icon: generic cloud — role: 'Hosts application components without vendor branding'. Use arrows with short English labels: Browser to API Gateway 'HTTPS POST command' and 'HTTPS GET query'; API Gateway to Command Handler 'Validated JSON command'; Command Handler to Event Store Database 'Append event(s)'; Event Store Database back to Command Handler 'Expected version OK' or '409 Conflict'; Event Store Database to Message Queue / Event Bus 'Committed domain event'; Message Queue / Event Bus to Projection Worker 'Event subscription'; Projection Worker to Read Model Database 'Upsert projection'; Query API to Cache 'Read cache key'; Cache to Query API 'Cache hit'; Query API to Read Model Database 'SELECT view'; Query API to Browser 'JSON response'; Event Store Database to Monitoring / Audit Log 'Event metadata'; optionally show replay path from Event Store Database to Projection Worker labeled 'Replay stream'. Add small callouts for core concepts: 'Write model', 'Append-only log', 'Eventual consistency', 'Rebuild state by replay', 'CQRS-friendly read side'. Add a numbered legend 1-7 in English: 1. 'User sends a command from the browser to the API over HTTPS.' 2. 'API validates payload and forwards the command to the command handler.' 3. 'Command handler loads aggregate history from the event store and evaluates business rules.' 4. 'If valid, new domain events are appended atomically to the event store; on version mismatch return 409 Conflict.' 5. 'Committed events are published to the event bus for downstream consumers.' 6. 'Projection workers consume events and update read-model tables and cache entries asynchronously.' 7. 'User queries are served from the query API using cache and read models, while full state can be rebuilt later by replaying events.' Visually distinguish write side versus read side with separate columns or swimlanes. Emphasize immutable event records, ordered streams, asynchronous projections, and eventual consistency. Visual style: retro 1980s computing, blueprint cyan palette, neon-cyan linework on dark blueprint background, subtle CRT grid, vintage terminal UI accents, technical schematic mood, precise vector outlines, glowing arrows, clean hierarchy, readable labels, educational but not claiming audited security. Include 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).