In shortWhat serverless means / Cold starts / When not to use it / Cost reality.
1. What serverless means
Your code runs when something calls it and sleeps when nothing does. You pay for the pecking, not for the roosting.
2. Cold starts
The first call after idle takes a little longer, like a hen getting off the perch. Keep a few instances warm if every millisecond matters.
3. When not to use it
Long-running jobs, steady heavy load, and anything that needs a persistent connection are often better in a nest.
4. Cost reality
For spiky traffic it is wonderfully cheap. For constant traffic, do the math before you celebrate.
Written by Bartholomew Brooder, Chief Financial Hen. Disagree? Tell us. We read every message, usually before the second coffee.