Three-Tier Web App Topology Layout Infographic

Tech architecture infographic titled "AWS Three-Tier Web App" using HOW-IT-WORKS archetype adapted as a lifecycle/state-oriented topology layout for a non-technical executive audience. Show a clean three-tier web application with clearly separated labeled boxes and directional arrows: Presentation Tier, Application Tier, Data Tier. Include these required component boxes with icons, canonical English names, and one-line English role descriptions: Browser — 'End-user client that sends HTTPS requests and renders pages'; Web Front End — 'Static or server-rendered UI layer handling user interaction'; API Service — 'Application logic layer exposing REST endpoints'; Cache — 'In-memory layer for fast session or query reuse'; Queue — 'Asynchronous task buffer for background processing'; Database — 'Persistent relational data store for application records'. Optionally add Load Balancer — 'Routes incoming traffic to healthy app instances' and Worker Service — 'Consumes queued jobs and updates data' to make the three-tier flow technically accurate. Arrange components left-to-right or top-to-bottom in a blueprint topology: Browser -> Web Front End / Load Balancer -> API Service -> Cache, Queue, Database, with Worker Service connected from Queue to Database. Use arrows with short English labels showing data direction and real protocol/data names: 'HTTPS request', 'HTML/CSS/JS', 'REST JSON', 'Cache read', 'Cache hit', 'Cache miss', 'Enqueue job', 'TCP query', 'SQL SELECT/INSERT', 'Job result', 'JSON response', 'HTTP 200'. Make the lifecycle explicit with numbered flow markers and a numbered legend 1-7 in English: 1. User opens app in Browser over HTTPS. 2. Front End serves interface and forwards API calls. 3. API Service validates request and checks Cache. 4. On cache miss, API queries Database over TCP/SQL. 5. API may place long-running work onto Queue. 6. Worker Service processes queued job and updates Database. 7. API returns JSON response and Front End renders result to Browser. Include subtle state-machine feel by visually grouping stages such as 'Request Received', 'Read Fast Path', 'Persistent Read/Write', 'Async Processing', 'Response Delivered', while still using boxes and arrows rather than abstract circles. Keep text simple and executive-friendly, avoiding implementation overload and avoiding any claim that this is a certified or audited reference architecture. Visual style: blueprint schematic, minimal monochrome palette, dark navy or charcoal background with white and light gray linework, restrained cyan accent for arrows and numbering, thin grid, technical drawing callouts, crisp vector outlines, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. No real cloud-vendor logos; if cloud context is needed, use only generic cloud icons. 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).