UML Diagramm Systemarchitektur mit API, Queue und Datenbank

Tech architecture infographic titled "UML Diagram" — SYSTEM ARCHITECTURE (services + queues + storage). Create a UML-inspired system architecture diagram for a mid-level developer, on a white canvas, using minimal flat design with a cool blue & cyan palette, clean spacing, subtle shadows, and a polished photorealistic infographic feel. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Show UML-style notation with actor, components, interfaces, and relationships.

Layout: left-to-right architecture flow with clearly labeled boxes and directional arrows. Include these components as UML-style boxes/components:
1. Actor: "User" — role description: "Initiates requests from the client side"
2. "Web Browser" — role description: "Renders UI and sends HTTPS requests"
3. "API Gateway / REST API" — role description: "Validates requests and routes them to services"
4. "Application Service Layer" — role description: "Executes business logic and coordinates workflows"
5. "Cache" — role description: "Stores frequently accessed transient data"
6. "Message Queue" — role description: "Buffers asynchronous tasks for reliable processing"
7. "Worker Service" — role description: "Consumes queued jobs and processes background tasks"
8. "Relational Database" — role description: "Persists structured application data"
9. "Generic Cloud" — role description: "Represents hosted infrastructure environment"

Connections and arrow labels in English:
- User → Web Browser: "User action"
- Web Browser → API Gateway / REST API: "HTTPS request"
- API Gateway / REST API → Application Service Layer: "REST call / JSON payload"
- Application Service Layer → Cache: "GET/SET cached data"
- Cache → Application Service Layer: "Cache hit / cached value"
- Application Service Layer → Relational Database: "SELECT / INSERT / UPDATE"
- Relational Database → Application Service Layer: "Query result / committed row"
- Application Service Layer → Message Queue: "Enqueue async job"
- Message Queue → Worker Service: "Queued message"
- Worker Service → Relational Database: "Write processing result"
- Application Service Layer → API Gateway / REST API: "Service response"
- API Gateway / REST API → Web Browser: "HTTP 200 JSON response"

UML-inspired visual cues:
- Actor icon for User
- Component-style boxes with small technical icons for Browser, API, Service, Cache, Queue, Worker, Database, Cloud
- Dashed or clean dependency connectors where appropriate, but keep primary flow arrows solid and directional
- Optional interface lollipop or stereotype labels like <<component>> and <<actor>> in tasteful UML style
- Keep the diagram technically accurate and easy to read

Add a numbered legend (1-7) in English at the bottom or right side:
1. "User interacts with the browser UI to trigger an application request."
2. "The browser sends an HTTPS request to the API Gateway / REST API."
3. "The API validates the request and forwards a JSON payload to the application service layer."
4. "The service checks the cache first; on a miss, it queries the relational database."
5. "The service returns the result and may store reusable data in the cache."
6. "If background work is needed, the service publishes an async job to the message queue."
7. "A worker consumes the queued message, processes the task, updates the database, and the client receives an HTTP 200 response for the main request."

Overall mood: professional, precise, modern, calm, developer-friendly, architecture-documentation quality. All labels must be crisp and readable, with balanced whitespace and clean alignment. 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).