AWS Web Application Diagram: Event Sourcing Pattern Flow

Tech architecture infographic titled "Event Sourcing Pattern" using archetype HOW-IT-WORKS with state machine / lifecycle emphasis. Show a blueprint schematic of an event-sourced application as a clean lifecycle diagram with labeled boxes and directional arrows. Include these components as clearly separated vector boxes with icons, English names, and one-line English role descriptions: Browser — "User interface sends commands and reads views"; API Gateway / REST API — "Validates request and routes commands"; Command Handler — "Executes business rules and creates domain events"; Aggregate — "Applies current state rules before accepting changes"; Event Store — "Appends immutable domain events in order"; Snapshot Store — "Stores periodic aggregate snapshots for faster rehydration"; Message Queue / Event Bus — "Publishes committed events to subscribers"; Projection Worker — "Builds read models from event stream"; Read Model DB — "Serves query-optimized views"; Cache — "Accelerates frequent read queries"; Monitoring / Audit Log — "Tracks processing status and event metadata"; Generic Cloud Boundary — "Application runs in generic cloud environment". Connect all boxes with arrows showing accurate data flow and lifecycle transitions. Required flow: Browser -> API Gateway / REST API labeled "HTTPS JSON command"; API Gateway / REST API -> Command Handler labeled "validated command"; Command Handler -> Aggregate labeled "load aggregate state"; Aggregate <- Event Store labeled "event stream replay"; Aggregate <- Snapshot Store labeled "latest snapshot"; Aggregate -> Command Handler labeled "decision result"; Command Handler -> Event Store labeled "append domain event"; Event Store -> API Gateway / REST API labeled "201 Created / 409 Conflict"; Event Store -> Message Queue / Event Bus labeled "published event"; Message Queue / Event Bus -> Projection Worker labeled "event subscription"; Projection Worker -> Read Model DB labeled "upsert projection"; Read Model DB -> Cache labeled "cached query result"; Browser -> API Gateway / REST API labeled "HTTPS read query"; API Gateway / REST API -> Cache labeled "lookup view"; Cache -> API Gateway / REST API labeled "cache hit"; API Gateway / REST API -> Read Model DB labeled "query projection"; Read Model DB -> API Gateway / REST API labeled "JSON response"; Event Store -> Monitoring / Audit Log labeled "event metadata"; Projection Worker -> Monitoring / Audit Log labeled "processing metrics". Visually distinguish write side and read side, with the write path on the left, event log in the center, asynchronous projection path to the right, and query-serving path at the bottom. Add subtle lifecycle/state annotations around the Aggregate box: "Command Received", "State Rehydrated", "Rules Evaluated", "Event Created", "Event Committed", "Projection Updated", "View Queried". Include a numbered legend 1-7 in English: 1. Client sends a command over HTTPS to the API. 2. The command handler validates intent and loads aggregate state from snapshot plus event replay. 3. The aggregate evaluates business rules and emits one or more domain events. 4. The event store appends immutable events atomically and returns 201 Created or 409 Conflict on version mismatch. 5. Committed events are published to the queue / event bus for asynchronous subscribers. 6. Projection workers update read-model tables and refresh cached views. 7. Clients query the read model through the API and receive a JSON response. Style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a minimal monochrome palette, white or dark-blue blueprint background, thin technical linework, subtle grid, precise arrows, architectural schematic mood, staff-level clarity, restrained contrast, no vendor branding, generic cloud icons only. Make it technically accurate for event sourcing and CQRS-style read projections, but not framed as 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).