Serverless Cold Start Infographic for Network Topology Design

Tech architecture infographic titled "Serverless Cold Start" using SYSTEM ARCHITECTURE (services + queues + storage). Show an isometric tech diagram for a mid-level developer explaining how a serverless request experiences cold start latency and then warms up. Create labeled boxes connected by directional arrows, with each box containing an icon, a canonical English component name, and a one-line English role description. Include these components: Browser — 'User client sending HTTPS requests'; API Gateway — 'Routes REST requests to serverless backend'; Auth Service — 'Validates JWT or OAuth access token'; Serverless Function Router — 'Dispatches request to function runtime'; Cold Start Trigger — 'No warm instance available, new runtime needed'; Runtime Provisioner — 'Allocates isolated compute environment'; Function Container — 'Loads code package and dependencies'; Initialization Phase — 'Bootstraps runtime, config, and connections'; Warm Function Instance — 'Handles request after startup completes'; Cache — 'Stores hot data and session-friendly lookups'; Queue — 'Buffers async jobs for background processing'; Worker Function — 'Consumes queued jobs in separate execution'; Database — 'Persists application records via TCP connection'; Object Storage — 'Holds deployment package and assets'; Monitoring — 'Collects latency, cold start, and error metrics'; Generic Cloud Boundary — 'Serverless platform environment'. Use arrows with short English labels showing proper flow and payloads: Browser to API Gateway labeled 'HTTPS request'; API Gateway to Auth Service labeled 'JWT token' or 'OAuth token'; Auth Service to API Gateway labeled '200 OK / 401 Unauthorized'; API Gateway to Serverless Function Router labeled 'REST event JSON'; Router to Cold Start Trigger labeled 'No warm instance'; Cold Start Trigger to Runtime Provisioner labeled 'Provision runtime'; Runtime Provisioner to Object Storage labeled 'Fetch code package'; Object Storage to Function Container labeled 'Code bundle'; Function Container to Initialization Phase labeled 'Load runtime'; Initialization Phase to Cache labeled 'Warm lookup'; Initialization Phase to Database labeled 'Open TCP connection'; Initialization Phase to Warm Function Instance labeled 'Init complete'; Warm Function Instance to Database labeled 'SELECT / INSERT'; Warm Function Instance to Cache labeled 'GET / SET'; Warm Function Instance to Queue labeled 'Async job'; Queue to Worker Function labeled 'Event message'; Worker Function to Database labeled 'UPDATE row'; Warm Function Instance back to API Gateway labeled 'JSON response'; API Gateway back to Browser labeled '200 OK'; all key services also sending arrows to Monitoring labeled 'Latency metric', 'Cold start metric', 'Error log'. Add visual distinction between cold path and warm path: cold path highlighted with brighter neon green and amber latency markers, warm path in stable green. Include small timing callouts such as 'Container provisioning', 'Runtime initialization', 'Dependency loading', 'Connection setup', and 'Warm reuse' as English labels near the relevant boxes. Add a numbered legend 1-7 in English: 1. Browser sends an HTTPS request to API Gateway. 2. API Gateway validates JWT or OAuth and forwards a REST event. 3. If no warm instance exists, the platform provisions a new runtime. 4. The function code and dependencies are loaded, then initialization runs. 5. The initialized function accesses cache, database, or queue as needed. 6. The function returns a JSON response through API Gateway to the browser. 7. Subsequent requests reuse the warm instance until it is recycled, reducing latency. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a green terminal palette with dark charcoal background, phosphor green highlights, muted emerald surfaces, soft grid lines, subtle amber accents for latency hotspots, crisp thin outlines, minimal glow, clean spacing, modern technical mood, precise network-topology design feel. Emphasize that this is an explanatory architecture illustration, 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).