Burnt $72k testing Firebase and Cloud Run and almost went bankrupt

Re:Burnt $72k testing Firebase and Cloud Run and almost went... by vp8989 on Thursday December 10, 2020 @07:17PM (#25380682)

"The downside of disabling active resources is huge. It would mean a catastrophic interruption to the customers application exactly when its the most popular/active."

Lol what ... this is exactly what happens any time you hit a rate limit on any AWS service. The customers application is "catastrophically interrupted" during its most popular/active period.

The only difference is in that case, it suits AWS to do that whereas in the case of respecting a billing limit, it doesn't.

[ Parent | on HN ]

Re:Burnt $72k testing Firebase and Cloud Run and almost went... by howlgarnish on Thursday December 10, 2020 @09:18PM (#25381478)

If you hit a rate limit, the marginal portion of requests exceeding that limit is dropped: if you plot the requests, the graph gets clipped. Bad, but not catastrophic.

If you hit a billing limit, everything beyond that point is dropped, and the graph of requests plunges to zero. You're effectively hard down in prod.

[ Parent | on HN ]

Re:Burnt $72k testing Firebase and Cloud Run and almost went... by franciscop on Saturday December 12, 2020 @11:23AM (#25399258)

And for some companies/individuals, if you keep charging then THEY will plunge to a large negative debt. It's not even zero, it's a lot worse than that.

[ Parent | on HN ]

Re:Burnt $72k testing Firebase and Cloud Run and almost went... by freemint on Friday December 11, 2020 @07:01AM (#25384800)

Just as it is with bank accounts. Once you run out of money you hit a hard floor.

[ Parent | on HN ]