Network Topology Design for Serverless Cold Start Flow

Tech architecture infographic titled "Serverless Cold Start" using REQUEST FLOW (client → server → DB) archetype. Show a technically accurate request path that explains cold-start latency in a serverless application. Create labeled boxes connected by directional arrows in a clean left-to-right flow with optional top/bottom support components. Main boxes: Browser Client, CDN / Edge, API Gateway, Auth Service, Serverless Function Router, Cold Start Init Phase, Warm Function Instance, Cache, Database, Message Queue, Observability. Each box must include an icon, a canonical English component name, and a one-line English role description. Example role descriptions: Browser Client — "Sends HTTPS request and renders response"; API Gateway — "Validates route and forwards request to compute"; Cold Start Init Phase — "Allocates runtime, loads code, initializes dependencies"; Warm Function Instance — "Executes handler after initialization"; Cache — "Serves hot data to reduce database reads"; Database — "Stores persistent application records"; Message Queue — "Buffers asynchronous background jobs"; Observability — "Collects logs, metrics, and traces". Show arrows with short English labels describing payloads and protocol details: Browser to CDN / Edge: "HTTPS request"; CDN / Edge to API Gateway: "REST request"; API Gateway to Auth Service: "JWT validation"; API Gateway to Serverless Function Router: "Invoke function"; Router to Cold Start Init Phase: "No warm instance"; Cold Start Init Phase to Warm Function Instance: "Runtime boot + code load"; Warm Function Instance to Cache: "GET key"; Cache to Warm Function Instance: "Cache miss / hit"; Warm Function Instance to Database: "SELECT / INSERT row over TCP"; Warm Function Instance to Message Queue: "Enqueue async job"; Warm Function Instance to API Gateway: "JSON response, HTTP 200"; API Gateway to Browser Client: "HTTPS response"; all major components to Observability: "Logs / metrics / traces". Emphasize the cold-start branch visually with a highlighted latency band, startup stopwatch icon, and annotations such as "Container provisioning", "Runtime initialization", "Dependency loading", "Connection setup", while also showing the warm-path shortcut that bypasses initialization. Include small latency badges like "cold: 400-1200 ms" and "warm: 20-80 ms" as illustrative, non-audited example metrics. Add a numbered legend 1-7 in English walking through the lifecycle: 1. Client sends an HTTPS request to the API endpoint. 2. API Gateway authenticates or validates JWT and selects the serverless route. 3. If no warm instance exists, the platform starts a new function environment. 4. Runtime boots, code and dependencies load, and outbound connections initialize. 5. The function executes business logic, checks cache, and reads or writes the database. 6. Optional asynchronous work is pushed to the queue while logs and metrics are emitted. 7. API Gateway returns a JSON response to the client; later requests may hit a warm instance and avoid cold-start delay. Add a subtle note in English that this is an explanatory architecture view, not an audited reference architecture. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Aesthetic: cyberpunk neon with warm beige and navy palette, glowing accent lines, soft grid background, high contrast, futuristic but professional, architect-grade clarity, elegant spacing, crisp icons, precise arrows, restrained neon highlights around the cold-start path. 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).