SolarWinds Diagram of Event Sourcing Pattern Flow

Tech architecture infographic titled "Event Sourcing Pattern" using PROTOCOL HANDSHAKE (numbered exchanges). Show a beginner-friendly how-it-works diagram of event sourcing with labeled flat vector boxes connected by directional arrows. Include these boxes: 1) Browser — icon: web browser — role: "User sends command request". 2) API Gateway / REST API — icon: endpoint/server — role: "Validates command and routes request". 3) Command Handler — icon: gear/service — role: "Applies business rules and creates domain events". 4) Event Store DB — icon: database — role: "Appends immutable event records". 5) Message Queue / Event Bus — icon: queue/topic — role: "Publishes events to subscribers". 6) Projection Service — icon: stacked layers/service — role: "Builds read models from events". 7) Read Model DB — icon: database — role: "Stores query-optimized views". 8) Cache — icon: lightning/cache — role: "Serves hot read results quickly". 9) Query API — icon: API/service — role: "Returns current state to clients". Arrange the flow as a numbered protocol-style exchange sequence with arrows and exchange numbers. Arrows must include short English labels such as: "1. HTTPS POST command", "2. Validate + authorize", "3. Create domain event", "4. APPEND event", "5. Event persisted", "6. Publish event", "7. Consume event", "8. Update projection", "9. UPSERT read model", "10. Cache refresh", "11. HTTPS GET query", "12. JSON response". Make the technical flow accurate: commands write to the Event Store first, events are immutable append-only records, projections asynchronously update read models, reads come from Read Model DB or Cache rather than replaying the write store on every request. Show optional generic cloud boundary icons only, with no vendor branding. Add a small caution note in English: "Conceptual developer diagram, not an audited reference architecture". Include a numbered legend (1-7) in English walking through lifecycle: 1. User sends a command over HTTPS. 2. API validates input and passes command to handler. 3. Command handler checks business rules and emits one or more domain events. 4. Event Store DB appends immutable events in order. 5. Event Bus publishes persisted events to downstream consumers. 6. Projection Service updates Read Model DB and optionally Cache. 7. Query API serves current state from read models as JSON. Visual style: minimal flat, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a developer pink & teal palette with soft neutral background, crisp outlines, subtle shadows, clean spacing, modern onboarding-friendly mood, simple icons, high readability, balanced composition. Audience is curious beginner, so keep structure clear, non-intimidating, and visually explanatory. 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).