Top
Best
New

Posted by operator-name 9/7/2025

Serverless Horrors(serverlesshorrors.com)
626 points | 484 commentspage 5
gangtao 9/8/2025|
I got a large GCP logstorage bill as my applicatino is writing too much logs
cgijoe 9/8/2025||
Title should really be "Cloud Hosting Horrors", not serverless per se.
tempodox 9/7/2025||
How are all these cases of exorbitant surprise bills not prosecuted as fraud?
ChrisMarshallNY 9/7/2025||
At one time, I considered using Firebase as a backend, but then, I kept reading stories like these, and decided to roll my own. I'm fortunate to be able to do that.

It's kind of amazing, though. I keep getting pressure from the non-techs in my organization to "Migrate to the Cloud." When I ask "Why?" -crickets.

Industry jargon has a lot of power. Seems to suck the juice right out of people's brains (and the money right out of their wallets).

jppope 9/7/2025||
This is a weird take on an incredibly useful paradigm (serverless). One the one side, there are obviously precautions that all of these users could have taken to avoid these charges on the other hand its totally common to spin up a thing and forget about it or not do your due diligence. I totally feel for the people who have been hit with these chargers.

At the end of the day though the whole think feels like a carpenter shooting themselves in the foot with a nail gun then insisting that hammers are the only way to do things.

zkmon 9/7/2025||
Maintaining your own containers or VMs is hard considering how much risk appetite you have for the issues at infra level. So, yeah, when you complain about the costs of serverless, you are just paying for your low risk appetite low cost of your IT management.
themafia 9/7/2025||
An alternative title might be "Failure to read the documentation horrors."

If you didn't sit down with the documentation, the pricing guide, and a calculator before you decided to build something then you share a significant portion of the fault.

stressback 9/7/2025||
I read a lot of the posts at the little blog here and, uh, every single one sounds like a complete amateur making a cloud configuration mistake. I haven't found one that is the provider's fault or the fault of "serverless"

I would be embarrassed to put my name on these posts admitting I can't handle my configs while blaming everyone but myself.

Serverless isn't a horror, serverlesshorrors poster. You are the horror. You suck at architecting efficient & secure systems using this technology, you suck at handling cloud spend, and you suck at taking responsibility when your "bug" causes a 10,000x discrepancy between your expected cost and your actual bill.

Just because you don't understand it doesn't mean it sucks

Cpoll 9/7/2025||
You're not wrong about cloud configuration mistakes, but a tool that lets you increase costs 10000x (without even letting you set a safety) is a hell of a chainsaw.

I'm more worried about the overconfident SRE that doesn't stay up at night worrying about these.

bhk 9/7/2025|||
Consider this analogy: Instead of using a root command shell, it is wise to use an account with appropriately restricted capabilities, to limit the downsides of mistakes. Cloud services support the notion of access control, but not the notion of network resource usage limits. It's an architectural flaw.

Or do you always log in as root, like a real man, relying purely on your experience and competence to avoid fat-finger mistakes?

Bluecobra 9/7/2025|||
That being said, the cloud providers could do a better job explaining to new/naive users that great power comes with great responsibility and there is no hand holding. Someone might be more hesitant to willy nilly spin up something if a wizard estimates that the maximum cost could be $X per month.
McGlockenshire 9/7/2025|||
> every single one sounds like a complete amateur making a cloud configuration mistake

Golly if only the configuration wasn't made this way on purpose exactly to cause this exact problem.

webdevver 9/7/2025||
truth nuke
luxuryballs 9/7/2025||
there should be some kind of insurance for bugs that introduce unusually expensive usage
mdaniel 9/7/2025|
I believe any such policy would need its premiums based on the services used (and likely the qualifications of the staff) since, unlike rebuilding a house, the financial risk is almost unlimited with out of control cloud spend

It reminds me of the Citi(?) employee who typed the wrong decimal place in a trade: computers make everything so easy!

rjakobsson 9/8/2025|
Hahaha, this is awesome!
More comments...