Diagrama de bloque ejemplos: microservicios vs monolito

Tech architecture infographic titled "Microservices vs Monolith" using HOW-IT-WORKS archetype, adapted as a side-by-side lifecycle comparison for a non-technical executive audience. Create a clean split-layout with two parallel columns: left column for Monolith, right column for Microservices, each shown as a labeled state/lifecycle flow with boxes and arrows. Include labeled boxes for Browser, API, Database, Cache, Queue, and service/application layers where relevant, all connected with arrows showing data direction. In the Monolith column, show: Browser, Load Balancer or Web Entry, Monolithic Application, Shared Database, optional Cache, optional Queue. In the Microservices column, show: Browser, API Gateway, Auth Service, User Service, Order Service, Notification Service, Cache, Queue, and Database-per-service or Service Datastores. Each box must include a simple tech icon, a canonical English name, and a one-line English role description. Example box text style: "Browser — User client sending HTTPS requests", "API Gateway — Routes REST requests to services", "Shared Database — Stores all application data", "Queue — Buffers asynchronous events". Use arrows with short English labels such as "HTTPS request", "REST call", "JWT token", "SQL query", "Cache read", "Publish event", "JSON response", "Async message". Show technically accurate flow: Browser sends HTTPS request, edge/API layer forwards to app or services, services read/write datastore, cache serves repeated reads, queue handles asynchronous work, response returns as JSON or HTML with HTTP 200 OK where appropriate. Include lifecycle/state emphasis by visually marking numbered stages from request arrival to processing, persistence, async work, and response. Add a numbered legend 1-7 in English explaining the lifecycle: 1. Client sends HTTPS request, 2. Entry layer receives and routes traffic, 3. Application logic executes, 4. Data is read from cache or database, 5. Optional async work is sent to queue, 6. Components update state and persist data, 7. Response returns to client. Add concise comparison callouts in English for executives: "Single deploy unit", "Shared release cycle", "Centralized scaling" on monolith side; "Independent services", "Service-level scaling", "Isolated failures" on microservices side. Include a subtle note in English that this is a conceptual comparison diagram, not an audited reference architecture. Visual style: blueprint schematic, minimal monochrome palette, white or pale lines on dark navy or charcoal background, thin grid, technical drafting feel, restrained contrast, minimal shading, precise geometric boxes, simple arrows, clear hierarchy, spacious composition, executive-friendly readability. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. 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).