Re:Incident with GitHub Actions and Codespaces
by OJFord on Thursday April 14, 2022 @06:11AM
(#31024996)
I also think it'd be good for companies. If you usually pay (say, numbers don't matter, except that AWS or whoever doesn't care until they get bigger I suppose) 1k-3k and set a 'don't surprise me too much' limit of 5k, then when something unexpected happens, instead of having a bad time pleading with them to let you off 12k or whatever and feeling cautious about using it again perhaps with some sour taste even if they do let you off, you think 'woah, glad I have the limit', and pretty much get on with your day; AWS or whoever gets an unexpected 2-4k instead of writing off 9-11k, and keeps the happy customer (at the customer's expense instead of its own).
Re:Incident with GitHub Actions and Codespaces
by bencollier49 on Thursday April 14, 2022 @03:48PM
(#31032370)
I agree, unless... It could be that they're making most of their money from spikes. It would be interesting if that were the case.
Re:Incident with GitHub Actions and Codespaces
by OJFord on Thursday April 14, 2022 @07:38PM
(#31034896)
I don't think so, surely most comes from far bigger fish than the type to have (not have time/resources to avoid) spikes and care about them.
Re:Incident with GitHub Actions and Codespaces
by Dave3of5 on Thursday April 14, 2022 @04:59AM
(#31024667)
I agree cloud providers shouldn't be able to bankrupt their users due to high usage. IMO it should be mandatory to set a limit it makes sense from a finance side.
In my case my cards don't have $12 million of a limit so they could not actually charge me that amount of money. It makes sense if you use invoice type billing i.e. like a company but as an individual these insane bills can't actually run.
It would be a pro-innovation law because people would then have the confidence to innovate.