Diagramm Arten für KI- und Softwaresysteme Infografik

Tech architecture infographic titled "Diagram Types in AI and Software Systems" using HOW-IT-WORKS archetype. Create a clear beginner-friendly overview of common technical diagram types, with a central top-level architecture strip showing labeled boxes connected by arrows: Browser, API Server, Cache, Message Queue, Database. Each box must include a simple icon, the component name in canonical English, and a one-line role description in English: Browser — 'User client sending requests'; API Server — 'Handles business logic and endpoints'; Cache — 'Stores frequently accessed data'; Message Queue — 'Buffers asynchronous jobs'; Database — 'Persists application records'. Show arrows with English labels and correct direction: Browser -> API Server 'HTTPS request', API Server -> Cache 'Cache lookup', Cache -> API Server 'Cache hit / miss', API Server -> Database 'SQL query', Database -> API Server 'Rows / result set', API Server -> Message Queue 'Enqueue job', Message Queue -> API Server 'Async event', API Server -> Browser 'JSON response 200 OK'. Add five side-by-side mini example panels underneath, each visually distinct but stylistically consistent, each with boxes, arrows, labels, and a small title. Panel 1: '1. Request Flow' with Browser -> Load Balancer -> API -> Database, arrow labels 'HTTPS GET /items', 'Forward request', 'SELECT query', 'JSON 200 OK', note 'Use for tracing a single user request'. Panel 2: '2. System Architecture' with Web App, Auth Service, API Service, Cache, Queue, Worker, Object Storage, Database, arrows labeled 'REST', 'JWT validation', 'Read/write', 'Publish event', 'Consume job', 'Store file', note 'Use for showing major components and integrations'. Panel 3: '3. Protocol Handshake' with Client and Server, numbered exchanges 1-4: 'ClientHello', 'ServerHello + certificate', 'Key exchange', 'Encrypted HTTP request', note 'Use for explaining connection setup such as TLS handshake'. Panel 4: '4. Data Pipeline' with Source DB -> Extractor -> Transformer -> Data Warehouse -> BI Dashboard, arrow labels 'CDC / export', 'Raw records', 'Cleaned schema', 'Analytics query', note 'Use for data movement and ETL / ELT workflows'. Panel 5: '5. State Machine' with rounded boxes and directional arrows for 'Idle', 'Loading', 'Success', 'Error', transitions labeled 'Start request', '200 OK', 'Retry', 'Timeout / 500', note 'Use for modeling status transitions and app logic'. Add a numbered legend 1-7 walking through how to read and when to use these diagrams: 1 'Start with the user-facing request path', 2 'Follow arrows to see data direction', 3 'Read box descriptions to learn each component role', 4 'Use Request Flow for one transaction', 5 'Use System Architecture for service relationships', 6 'Use Protocol Handshake or Data Pipeline for specialized flows', 7 'Use State Machine for lifecycle transitions'. Visual style: minimal flat, cool blue and cyan palette, polished editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, lots of white space, balanced spacing, subtle shadows, crisp icons, approachable for curious beginners, clean infographic composition. All text rendered cleanly in English, no spelling errors, no gibberish characters, 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).