Event Sourcing Pattern Network Sketch Infographic

Tech architecture infographic titled "Event Sourcing Pattern" using SYSTEM ARCHITECTURE archetype (services + queues + storage). Show an isometric tech diagram for a mid-level developer, designed as a clear network sketch with vector-clean infographic layout. Scene composition: left-to-right distributed system with labeled boxes and directional arrows. Include these boxes: 1) Web Client — icon: browser window — role: "Sends commands and reads projections"; 2) API Gateway — icon: gateway / endpoint node — role: "Authenticates requests and routes commands"; 3) Command Service — icon: microservice cube — role: "Validates intent and creates domain commands"; 4) Aggregate / Domain Logic — icon: gear + entity — role: "Applies business rules and emits domain events"; 5) Event Store — icon: append-only database cylinder — role: "Persists immutable event stream by aggregate"; 6) Message Broker — icon: queue / topic — role: "Publishes events to subscribers asynchronously"; 7) Projection Worker — icon: worker node — role: "Builds read models from ordered events"; 8) Read Model Database — icon: query DB cylinder — role: "Stores denormalized views for queries"; 9) Cache — icon: cache stack — role: "Accelerates hot read responses"; 10) Query API — icon: API service box — role: "Serves queries from projections and cache"; 11) Monitoring / Replay Tool — icon: terminal panel — role: "Inspects streams and replays events"; 12) Generic Cloud Boundary — icon: neutral cloud — role: "Hosts application components". Connect with arrows and English labels: Web Client -> API Gateway labeled "HTTPS + JWT command request"; API Gateway -> Command Service labeled "REST/JSON command"; Command Service -> Aggregate / Domain Logic labeled "Validate command"; Aggregate / Domain Logic -> Event Store labeled "Append events"; Event Store -> Message Broker labeled "Published domain events"; Message Broker -> Projection Worker labeled "Event subscription"; Projection Worker -> Read Model Database labeled "Upsert projection"; Query API <-> Cache labeled "Cache lookup / cache set"; Query API -> Read Model Database labeled "Query projection"; Web Client -> Query API labeled "HTTPS read request"; Query API -> Web Client labeled "JSON response 200"; Monitoring / Replay Tool -> Event Store labeled "Replay stream"; Event Store -> Projection Worker labeled "Historical events". Add small technical notes near flow where accurate: "Optimistic concurrency check", "Ordered event stream", "At-least-once delivery", "Eventual consistency", "Immutable audit trail". Include optional side labels on storage: Event Store partitions by aggregate ID, Read Model optimized for queries. Add numbered legend 1-7 in English: 1. "Client sends a command over HTTPS with JWT to the API Gateway." 2. "Command Service validates intent and loads aggregate state from prior events." 3. "Domain logic decides whether the command is valid and emits new domain events." 4. "Event Store appends events atomically using optimistic concurrency control." 5. "Stored events are published through the message broker to downstream subscribers." 6. "Projection workers consume events and update read-model tables and cache asynchronously." 7. "Client queries the Query API, which returns a 200 JSON response from cache or read database." Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout; green terminal palette with dark graphite background, neon green highlights, muted emerald surfaces, subtle grid, soft glow edges, crisp arrows, high contrast labels, professional but approachable mood. Add compact title and section headers, balanced spacing, modular boxes, no vendor branding, no exaggerated security claims, clearly educational not 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).