Why serverless matters more than it looks

Most teams know this matters. Fewer have decided who owns it. Serverless is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Operability is a feature, and it has to be built rather than bought. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

Why this earns attention

Excellent for spiky, event-shaped workloads. There is a version of this that is over-engineered, and it is worth avoiding. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

Cold starts and vendor coupling are the real trade-offs. This is the sort of thing that compounds, quietly, in both directions. Doing this properly once is usually cheaper than doing it approximately three times.

Where it usually goes wrong

Cost modelling matters more here than anywhere else. Small and consistent beats large and occasional here. Assume whoever inherits this will have half your context and none of your patience.

In practice

The bill is a design document: it tells you exactly what your architecture actually does. Three things worth confirming about serverless before you move on:

• Someone can say what the current setup is without going to look
• Cost modelling matters more here than anywhere else — and you know whether that is true here
• There is a way to tell whether the last change to this helped

None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.