News for hackers. Stuff that matters.

A comment on How we spent $30k in Firebase in less than 72 hours. Parent comment

Re:How we spent $30k in Firebase in less than 72 hours by paranoidrobot on Wednesday August 01, 2018 @09:22PM (#17668564)
This seems like an overly cynical/snarky response.

It's not an unreasonable request that for services which advertise the ability to scale up and down on demand, that the billing and billing limits should also be able to respond similarly.

[ Parent | on HN ]
Re:How we spent $30k in Firebase in less than 72 hours by badlucklottery on Wednesday August 01, 2018 @10:51PM (#17668933)
>that the billing and billing limits should also be able to respond similarly

How so? With a pay-as-you-go system, firing off warnings and giving a projection of their future costs (which is hard when startups tend to have spikey traffic) is about as good as you can do.

Edit: I should add that the common solution to controlling your billing in situations like this is having some overflow path built into your beta app ("Sorry, we're not taking new users at the moment" or the like).

[ Parent | on HN ]
Re:How we spent $30k in Firebase in less than 72 hours by Dylan16807 on Thursday August 02, 2018 @12:23AM (#17669219)
The problem is that the user gets those alerts, tries to change the limit they set, and it doesn't work. That is definitely not as good as can be done.
[ Parent | on HN ]