Client Server Network Architecture Diagram: Kafka Pipeline

Tech architecture infographic titled "Kafka Pipeline Architecture" — REQUEST FLOW (client → server → processing → storage) for a curious beginner. Show a clean left-to-right client/server network architecture diagram with labeled boxes and directional arrows. Include these boxes: 1) Web Browser — icon: browser window — role: 'User sends event-producing requests'; 2) API Gateway / REST API — icon: server rack — role: 'Receives HTTPS requests and validates input'; 3) Producer Service — icon: microservice chip — role: 'Converts requests into Kafka messages'; 4) Kafka Broker Cluster — icon: queue / stream nodes — role: 'Durable event streaming and topic partition storage'; 5) Consumer Service — icon: worker gear — role: 'Reads messages from Kafka and processes events'; 6) Cache — icon: lightning database — role: 'Stores hot lookup data for fast reads'; 7) Operational Database — icon: cylinder database — role: 'Persists application state and processed records'; 8) Analytics / Data Sink — icon: warehouse cylinder — role: 'Stores event data for reporting'; optionally add Generic Cloud boundary — icon: cloud — role: 'Hosted infrastructure environment'. Connect every box with arrows showing accurate flow direction. Arrow labels in English: Browser to API Gateway 'HTTPS REST request'; API Gateway to Producer Service 'Validated JSON payload'; Producer Service to Kafka Broker Cluster 'Produce event via TCP'; Kafka Broker Cluster to Consumer Service 'Consume topic records'; Consumer Service to Cache 'Cache update'; Consumer Service to Operational Database 'INSERT / UPDATE row'; Consumer Service to Analytics / Data Sink 'Batch / stream write'; API Gateway back to Browser 'HTTP 202 Accepted' or 'HTTP 200 OK' for synchronous acknowledgement. If useful, show a dotted feedback arrow from Cache / Database back to API labeled 'Read model query result'. Make Kafka visually central, with topic lanes or partitions subtly indicated and labels such as 'Topic A', 'Partition 0', 'Partition 1'. Add small callouts for 'Producer', 'Broker', 'Topic', 'Consumer Group' in canonical English. Add a numbered legend 1-7 in English walking through the lifecycle: 1. Browser sends an HTTPS REST request to the API. 2. API validates the payload and forwards it to the producer service. 3. Producer serializes the event and publishes it to a Kafka topic over TCP. 4. Kafka brokers persist the record in partitions and make it available to consumers. 5. Consumer service reads the event as part of a consumer group. 6. Consumer updates cache and database, then optionally forwards data to analytics storage. 7. API returns acknowledgement to the browser, while downstream processing continues asynchronously. Include a small beginner-friendly note in English: 'Kafka decouples request handling from downstream processing'. Style: cyberpunk neon with warm beige and navy palette, glowing accents, dark navy background, beige panels, neon cyan / magenta edge lighting used sparingly, high contrast but readable, approachable and educational rather than intimidating. Composition: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, clear spacing, structured columns, subtle grid, modern captions, no vendor branding, no exaggerated security badges, not presented 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).