>as the consumer

This is where this discrepancy occurs. AWS (etc.) aren't targeting "consumers," they're targeting enterprises. Enterprises want to use these services with minimal interference and overhead. They'll build out whatever features they need as they need them. It's the same thing with any other utility service: a factory isn't interested in having the electric company or water company shut off their services if their usage spikes. They'll manage their usage (and potential overages) in whatever way is specifically suitable for them.

Consumers have plenty of options to prevent such situations. Hell, AWS even offers Lightsail which is the consumer-friendly version of their services which is designed to be simple with a flat rate cost (including options of object storage).

If a consumer decides to tap into enterprise-grade services and ends up getting burned as a result, then I'm blaming the consumer rather than the provider of those services. These dynamics are all pretty clear and easy to understand (and even mitigate, with enough effort), so I don't see how you can claim they are "opaque" unless you're the kind of consumer who feels every company should dumb down their products to cater to the lowest common denominator.

Especially when Google and co tells you that they can bill by the second.

I do not own a hyperscaler account as a private person and will never do, the financial risk is too high even IF the support will swift it away.

What does a "hard cap" do then? Delete all your resources? Because even stopped instances or unused volumes cost you.

Although I admit, there should be spend warnings.

If what you're doing makes money, the last thing you want is to stop doing the thing making you money. If, instead, it costs you money, don't wait until a usage surge to consider how to handle that – set it up now.

You also don't need any latency in the loop or moving parts that could wrongly interfere with the reliability of making that money.

Fortunately, the last thing this is is "opaque". You have all the observability you need to do what you want to do with unexpected usage.

What AWS (and every CSP) gives you is all the instrumentation and out of band tools to implement your own angel of death, to API kill a runaway thing if that's what you want to do.

You can also find countless TF and CDK patterns for it if you aren't sure how.

But please, no, do not ask to make critical systems subject to the whims of some billing decision enforcer.

The "why did they cut me off" complaints here far outnumber the "runaway bill" complaints.

I couldn't parse "Getting that model has meant taking on something else."

The article is 1000% ai slop

wrangler / workerd enables local CI

Yeah it's hard to read, so dry and AI

This looms nice and I starred but you just want actors and there are other options for that you might want to compare, I like rika actors, or temporal (not actors exactly but durable state and workflows). This is a space where a few very similar technologies after looked from different lenses sell themselves widely differently. So if you know what you want and the names of the things you are searching for you can get a thing that looks 90% like te rest, sorry a bit rambly. But yeah it would be nice to add some comparisons against these technologies as well.

Please don't submit AI-generated articles.