183
serverless
You do not run the server. You still own cold starts, limits, and the bill per invocation.
What is serverless?
Serverless runs a function or container on demand and scales it, including to zero. You trade operational control for limits: duration, payload size, concurrency, and local disk. Connections to databases from a burst of functions can exhaust the database.
Why does serverless matter when vibe coding?
Models move a long job or a chatty database client into a function. It times out or opens a thousand connections. Name the limits before the rewrite.
How do you do serverless?
Short, idempotent handlers. Pool or proxy database connections. No in-memory session. A long job belongs on a queue consumer with a real timeout, not a 15-minute function you hope finishes.
How do you ask a model for serverless?
This handler may run serverless. Keep it idempotent and under the time limit. Do not store session in memory. Do not open a database connection per invocation without a pooler. Long work goes to a queue.
What goes wrong with serverless?
Scale-to-zero on a route that has a cold start longer than the user’s patience. Warm it or do not use zero.