Troy Hunt and HIBP is a good example in the other direction but Hunt has also been burned plenty of times by serverless.

https://www.troyhunt.com/closer-to-the-edge-hyperscaling-hav...

Andras (author of Serverless Horrors) knows what he’s talking about.

The amount of brainwashing that big cloud providers have done, is insane.

We are building bare metal for our workloads… I don’t care if cloud is supposed to be cheaper because it never is. You can get a decent small business firewall to handle 10gbit fiber for $600 from unifi these days. Just another reason I’m glad I moved out of the Bay Area and nyc to a midwestern town for my company. I have a basement and can do rad things in my house to grow my business.

I've had this twice. Once with oracle, once with azure. They both charged me $2000-$5000 for simply opening and closing a database instance (used only for a single day to test a friend's open source project)

To be fair, support was excellent both times and they waived the bills after I explained the situation.

There should also be a general category for "cloud horrors" for things that cost $50k/month to host that would be $1500/month on a bare metal provider like Datapacket or Hetzner.

I'm old enough to remember when cloud was pitched as a big cost saving move. I knew it was bullshit then. Told you so.

Seem likes there are mistakes that were made on behalf of the users. The attackers found these mistakes and took advantage of them. i don't think "severless" is the problem.

In my experience: Fuck serverless.

If we're building anything bigger than a random script that does a small unit of work, never go for serverless. A company I recently worked for went with Serverless claiming that it would be less maintenance and overhead.

It absolutely was the worst thing I've ever seen at work. Our application state belonged at different places, we had to deal with many workarounds for simple things like error monitoring, logging, caching etc. Since there was no specific instance running our production code there was no visibility into our actual app configuration in production as well. Small and trivial things that you do in a minute in a platform like Ruby on Rails or Django would take hours if not days to achieve within this so-called blistering serverless setup.

On top of it, we had to go with DB providers like NeonDb and suffer from a massive latency. Add cold starts on top of this and the entire thing was a massive shitshow. Our idiot of a PM kept insisting that we keep serverless despite having all these problems. It was so painful and stupid overall.

I guess I'm missing something, why is this 'serverless' horrors? If anything it seems to specifically be serverful horrors.

I got a large GCP logstorage bill as my applicatino is writing too much logs