3 ms·

> What? Why wouldn't this just be an opt in thing? "Oh cool, I'll set a $1k cap, never gonna spend that on this little side proj." Fast forward a year, the sid

by remus 6y ago

> What? Why wouldn't this just be an opt in thing? "Oh cool, I'll set a $1k cap, never gonna spend that on this little side proj." Fast forward a year, the side proj has turned in to a critical piece of the business but the person who set it up has left and no one remembered to turn of the spending cap. Busy christmas shopping period comes along, AWS shuts down the whole account because they go over the spending cap, 6hr outage during peak hours, $20k sales down the pan. Of course it is technically the customers fault but it's a shit experience. Accidentally spending $72k is also technically the customers fault and also a shit experience. I don't think there is an easy solution to this problem.

freemint 6y ago
There exist totally a solution. It is also user hostile enough so it might get's adopted. $cloud_vendor just has to (and probably will) constantly nudge people to loosen the limit. Have a red banner that says, "you spend 3% of your monthly budget already think about increasing it". Also routinely send out emails to remind people. " Black Friday comes up think about increasing your quota " when your service has nothing to do with E-Commerce.
cogman10 6y ago
"Oh cool, I'll use spot instances, never gonna need reliability for this little side proj." "Oh cool, I'll only scale to 1 server, never gonna see high load for this little side proj." "Oh cool, I'll deploy only to US West 1, outages are never going to matter for this little side proj." There are a million ways to be out of money as a company. Why should this be any different? Why is the singular particular instance one where it is simply intolerable to accept that users can screw things up? There are lots of things that are "shit experiences" that are consumers fault. There is an easy solution. Give consumers the option and let them deal with the consequences. There are enough valid reasons to want hard caps on spending that it's crazy to not make it available because "Someone MIGHT accidentally set the limit too low which will cause them an outage in production that MIGHT mean they lose money"

by remus 6y ago

freemint 6y ago

There exist totally a solution. It is also user hostile enough so it might get's adopted. $cloud_vendor just has to (and probably will) constantly nudge people to loosen the limit. Have a red banner that says, "you spend 3% of your monthly budget already think about increasing it". Also routinely send out emails to remind people. " Black Friday comes up think about increasing your quota " when your service has nothing to do with E-Commerce.

cogman10 6y ago

"Oh cool, I'll use spot instances, never gonna need reliability for this little side proj." "Oh cool, I'll only scale to 1 server, never gonna see high load for this little side proj." "Oh cool, I'll deploy only to US West 1, outages are never going to matter for this little side proj." There are a million ways to be out of money as a company. Why should this be any different? Why is the singular particular instance one where it is simply intolerable to accept that users can screw things up? There are lots of things that are "shit experiences" that are consumers fault. There is an easy solution. Give consumers the option and let them deal with the consequences. There are enough valid reasons to want hard caps on spending that it's crazy to not make it available because "Someone MIGHT accidentally set the limit too low which will cause them an outage in production that MIGHT mean they lose money"