REST vs GraphQL infografía técnica para software para hacer topologias de red

Tech architecture infographic titled "REST vs GraphQL" using HOW-IT-WORKS archetype, side-by-side comparison layout for a mid-level developer audience. Show two parallel numbered flows: left column for REST request lifecycle, right column for GraphQL request lifecycle. Use labeled boxes connected by directional arrows. Include these components in both flows: Browser, API Gateway / API Server, Cache, Queue, Database. Add optional GraphQL Resolver layer in the GraphQL side and REST Endpoint layer in the REST side for technical accuracy. Each box must contain: a simple tech icon, a canonical English component name, and a one-line English role description. Example box descriptions: Browser — "User client sending HTTPS requests"; REST API Server — "Resource-based endpoints returning JSON"; GraphQL Server — "Schema-driven query execution layer"; Cache — "Stores frequent responses for faster reads"; Queue — "Processes asynchronous background jobs"; Database — "Persistent relational or document data store". Show arrows with short English labels describing what crosses. REST arrows: "HTTPS GET /users/42", "JSON resource", "Cache HIT", "SQL SELECT", "202 Accepted job". GraphQL arrows: "HTTPS POST /graphql", "GraphQL query", "Resolver fetch", "SQL SELECT", "JSON shaped response". Include numbered stages 1 through 7 over the flow, with a bottom or side legend in English walking through the lifecycle: 1. Client sends HTTPS request. 2. Server authenticates request using JWT or session if present. 3. REST routes to resource endpoint / GraphQL parses schema query. 4. Cache checked for reusable data. 5. Server fetches from Database and may enqueue async work. 6. Server assembles JSON response, with REST often fixed by endpoint and GraphQL shaped by selection set. 7. Browser renders data and may issue follow-up requests. Visually emphasize key contrast notes in small callout boxes: REST — "Multiple endpoints, resource-oriented, can over-fetch or under-fetch"; GraphQL — "Single endpoint, client-defined fields, resolver orchestration". Keep the flow technically accurate: REST commonly uses GET 200 OK, POST 201 Created, PATCH 200 OK or 204 No Content; GraphQL commonly returns 200 OK with data and possible errors array in JSON. Depict Browser, API, DB, cache, and queue as clean rectangular boxes with glowing edges, connected by arrows that clearly indicate direction. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Visual style: dark-mode developer UI aesthetic, dark background, neon cyan, neon magenta, electric blue, purple, subtle green accents, high contrast, precise grid alignment, modern terminal-inspired mood, professional but not vendor-specific. Add generic cloud and network icons only where helpful, no real cloud-vendor branding. Include a subtle note in English that this is a conceptual comparison diagram, not an audited reference architecture. 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).