Moca Wiring Diagram Style Three-Tier Web App Infographic

Tech architecture infographic titled "AWS Three-Tier Web App" using HOW-IT-WORKS archetype for a state-machine / lifecycle view, adapted for a non-technical executive audience. Show a clear three-tier system with labeled boxes and directional arrows in a simple lifecycle sequence: User Browser, Web Tier, Application API, Cache, Queue, Database, and Generic Cloud Boundary. Use generic cloud icons only, no vendor-specific branding. Layout should read left-to-right or top-to-bottom with large simple boxes, minimal cognitive load, and a clean numbered flow.

Include these labeled boxes with icon, canonical English name, and one-line English role description:
- Browser — "End user web client sending HTTPS requests"
- Web Tier — "Frontend layer serving pages and static assets"
- API — "Application logic handling REST requests and business rules"
- Cache — "In-memory layer storing hot session or query data"
- Queue — "Asynchronous message buffer for background tasks"
- DB — "Persistent relational database storing core application records"
- Generic Cloud — "Hosted infrastructure boundary for deployed services"

Connect them with arrows showing accurate data direction and short English labels:
- Browser -> Web Tier: "HTTPS GET / HTML, CSS, JS"
- Browser -> API: "HTTPS REST request"
- API -> Cache: "Read / write cached data"
- Cache -> API: "Cache hit value"
- API -> DB: "SQL query over TCP"
- DB -> API: "Rows / status"
- API -> Queue: "Enqueue background job"
- Queue -> API or Worker area: "Async task event"
- API -> Browser: "JSON response / HTTP 200"
- Web Tier -> Browser: "Rendered UI"

Represent the lifecycle as numbered stages with a visible legend 1-7 in English:
1. "User opens the web app in the browser over HTTPS."
2. "Web tier delivers the interface and forwards dynamic actions to the API."
3. "API validates the request and checks cache for reusable data."
4. "If needed, the API queries the database for persistent records."
5. "API stores or refreshes hot data in cache for faster future access."
6. "Long-running work is sent to the queue for asynchronous processing."
7. "API returns a JSON or rendered response to the browser with HTTP 200 or relevant status code."

Visually emphasize a three-tier grouping with subtle section labels:
- Presentation Tier
- Application Tier
- Data Tier
Optionally place Cache and Queue adjacent to the Application Tier as support components.

Style directions: blueprint schematic, minimal monochrome palette, dark navy or charcoal background with white and light gray linework, restrained technical accents, precise diagram spacing, thin vector strokes, executive-friendly simplicity, calm professional mood. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Avoid crowded low-level infrastructure details, avoid any claim that this is an audited or official reference architecture, and do not include any real cloud-vendor logos. 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).