Cyber Security Diagram: Event Sourcing Pattern Flow

Tech architecture infographic titled "Event Sourcing Pattern" using archetype REQUEST FLOW (client → server → DB), designed for a senior engineer audience. Show a precise event sourcing request flow with labeled boxes connected by directional arrows: Browser Client, API Gateway, Command API Service, Authentication Service, Event Store Database, Message Queue, Projection Worker, Read Model Database, Cache Layer, Query API Service, Monitoring / Logs, and Generic Cloud Boundary. Each box must include an icon, the component name in canonical English-tech form, and a one-line English role description. Use technically accurate event sourcing behavior: user action enters through Browser Client over HTTPS to API Gateway, API Gateway forwards REST request with JWT token to Command API Service, Command API validates command and appends immutable domain event to Event Store Database, Command API returns HTTP 202 Accepted or HTTP 201 Created depending on command outcome, Event Store publishes event to Message Queue over TCP, Projection Worker consumes event and updates Read Model Database, Query API Service reads denormalized state from Cache Layer or Read Model Database, Browser Client fetches current view from Query API Service over HTTPS as JSON response. Include arrows with short English labels such as: "HTTPS POST command", "JWT token", "Validate command", "Append event", "Stored event", "Publish domain event", "Consume event", "Update projection", "Cache read", "SQL query", "JSON response", "Telemetry". Make the event sourcing split visually explicit: write-side on the left-center with Command API Service and Event Store Database, read-side on the right-center with Query API Service, Cache Layer, and Read Model Database, queue and projection worker between them, browser at far left, monitoring/logs at bottom or top side receiving telemetry from services. Add subtle callouts for concepts relevant to senior engineers: immutable event log, eventual consistency, write model vs read model, append-only storage, asynchronous projection updates. Add a numbered legend 1-7 in English walking through the lifecycle: 1. User sends command from Browser Client to API Gateway over HTTPS. 2. API Gateway forwards authenticated REST request with JWT to Command API Service. 3. Command API validates business rules and appends a new immutable event to Event Store Database. 4. Command API returns HTTP 202 Accepted or HTTP 201 Created to acknowledge the command. 5. Event Store Database or publisher emits the domain event to Message Queue. 6. Projection Worker consumes the event and updates Read Model Database and Cache Layer asynchronously. 7. Browser Client requests current state from Query API Service, which reads from Cache Layer or Read Model Database and returns a JSON response. Visual style: cyberpunk neon with warm beige and navy palette, high contrast glowing edges, dark navy background, warm beige panels, neon accent lines in cyan and magenta, sophisticated but readable technical composition, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Overall mood: futuristic, analytical, precise, professional, not a marketing poster, not an audited reference architecture. No real cloud-vendor logos; use only generic cloud icons for the cloud boundary and infrastructure context. 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).