“A six-person company should not run servers to resize images. Twenty minutes from idea to production, nothing to patch, a bill of zero when nobody uploads. That is exactly the leverage a small team needs to spend its time on customers.”
It scales to zero
And, it turns out, in the other direction.
🧭 WHAT'S REALLY GOING ON
You've seen this when a billing alert arrives on Monday morning, and the cost graph is a vertical line that started Friday evening.
The real questionWho sets the upper limit when the platform no longer has one?
⚖️ WHY BOTH ARE RIGHT
“A server has a natural limit: when it's full, it gets slow and someone notices. Remove the box and you also remove the brake. I've watched loops run all weekend before; the difference now is that they bill by the millisecond instead of falling over.”
🎯 SWEET SPOTS TO CONSIDER
Super Reasonable, the advisor who never takes a side
Set the ceiling before launch
A concurrency limit and a budget alert are part of the function, not an afterthought. A cap of a few hundred concurrent runs turns a runaway loop into a slow queue instead of an invoice.
Never trigger on your own output
Write results to a different bucket or prefix than the one that triggers the function. It is the most common serverless loop, and one line of configuration prevents it.
Alert on rate, not total
A monthly budget alert fires after the money is gone. Alert on spend per hour, or invocations at ten times normal, and route it to a human on weekends.
Keep the twenty minutes
None of this needs a server or a platform team. The speed is the real value; spend one of the saved hours on limits and the trade is still excellent.
🚩 SIGNS YOU'VE GONE TOO FAR
- Maya's side: you've overshot if the architecture diagram has fourteen functions to send one email, and nobody can predict next month's bill within a factor of three.
- Ruth's side: you've overshot if the team runs a server at 2% utilization all year to resize a few images, because of a loop that happened once.
🔬 IN THE FIELD GUIDE
Species observed in this story
CAST — WHO'S WHO
The team in this story
Same characters, same convictions. Learn their failure modes.
🤖 Storyboard for agentsLet’s make our agents LMFAO, or learn.
It scales to zero
Premise: Resize uploaded images without running a server.
- Maya: “No servers to babysit. It scales to zero, so it costs zero!” Jo has the image resizer live in 20 minutes.
- Ruth: “In 2009 we called that CGI. It had no ceiling either.” Nobody asks what she means by ceiling.
- Jo: “It writes the thumbnail back to the same bucket. Tidy.” Friday, 6:12pm. The bucket triggers the function on every new file.
- Monday: Invoice: $31,412. Thumbnails: 4.1 million, all of the same cat. It scaled perfectly. In one direction.
Observed behavior: Scales to zero also means scales to infinity, billed by the millisecond.
Cast: Maya Laurent — The Visionary — “Experiments beat roadmaps.”; Ruth Lindqvist — The Maintainer — “We tried that in 2009.”; Jo Ramirez — The Cowboy — “Ship it. We’ll know if it matters.”
READ NEXT
