aws diagram as code Kafka Pipeline Architecture Infographic

Tech architecture infographic titled "Kafka Pipeline Architecture" using PROTOCOL HANDSHAKE (numbered exchanges) archetype. Create a minimal flat executive-friendly tech diagram that explains how a Kafka-based event pipeline works through numbered exchanges. Show labeled boxes connected by directional arrows in a clean left-to-right layout with subtle isometric depth or flat tech-diagram treatment. Include these components as boxes with icon, canonical English name, and one-line English role description inside each box: 1) Browser — "User Interface" — "Triggers business action and views status"; 2) API Gateway — "REST API" — "Receives HTTPS requests and validates input"; 3) Application Service — "Producer Service" — "Converts business events into Kafka messages"; 4) Cache — "Redis Cache" — "Stores hot state for fast reads"; 5) Queue — "Kafka Cluster" — "Durable event streaming and topic-based delivery"; 6) Queue detail — "Kafka Topic" — "Ordered event log split into partitions"; 7) Service — "Consumer Service" — "Reads events and executes downstream processing"; 8) DB — "Operational Database" — "Stores processed business records"; 9) Analytics Storage — "Data Lake / Warehouse" — "Stores events for reporting and analytics"; 10) Monitoring — "Metrics & Logs" — "Tracks lag, errors, throughput"; 11) Generic Cloud — "Cloud Network" — "Hosts distributed pipeline components". Use generic cloud icons only, no vendor branding.

Show protocol-accurate numbered exchanges with arrows and short English labels on each arrow: (1) Browser -> API Gateway, label "HTTPS POST /events"; (2) API Gateway -> Application Service, label "REST JSON request"; (3) Application Service -> Kafka Cluster, label "TCP Kafka Produce request"; (4) Kafka Cluster -> Application Service, label "Produce ACK"; (5) Kafka Cluster -> Consumer Service, label "TCP Kafka Fetch response"; (6) Consumer Service -> Operational Database, label "UPSERT row"; (7) Consumer Service -> Data Lake / Warehouse, label "Append event batch"; optional side arrows: Application Service -> Redis Cache, label "Cache status"; Consumer Service -> Metrics & Logs, label "Lag / error metrics"; API Gateway -> Browser, label "HTTP 202 Accepted". Emphasize that Kafka is the event backbone between producer and consumer services. Visually depict Kafka Topic partitions inside or beside the Kafka Cluster box with partition lanes and ordered messages.

Add a numbered legend 1-7 in English for non-technical exec readers: 1. "A user action sends an HTTPS request to the API." 2. "The API passes the business request to the producer service." 3. "The producer service publishes an event to a Kafka topic." 4. "Kafka stores the event durably and returns an acknowledgement." 5. "Consumer services fetch events from Kafka partitions." 6. "Consumers update operational systems and fast-access cache." 7. "Events also flow to analytics storage while monitoring tracks pipeline health." Include a small note in English: "Illustrative conceptual architecture, not an audited reference design."

Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Minimal flat composition, lots of whitespace, crisp geometric boxes, rounded corners, thin connector arrows, soft shadows, executive-friendly simplification, modern product-design aesthetic. Color palette: developer pink and teal with white background, dark slate text, teal arrows for primary flow, pink highlights for Kafka and event path, muted gray for secondary infrastructure, subtle gradients only if needed. Overall mood: clean, trustworthy, modern, concise, strategic overview for a non-technical executive. Avoid dense code or tiny text. No rendered search-intent text, no extra SEO text. 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).