Implementing this in any meaningful manner quickly begins to look like every read becoming a globally synchronised write. Of course it doesn't have to be perfect, but even approximating perfection doesn't look much different. Also, can you imagine the kind of downtimes and complaints that would inevitably originate from a fully synchronous billing architecture?
Prepaid only is a fantastic idea, until your site goes (desirably) viral and then gets shut off right as traffic is picking up, or you grow steadily and forget to increase your deposit amount and suddenly production is down. Billing alerts are a much better solution IMHO.
the planning-your-day-around-the-window thing is real and underrated as a cost. the limits don't just hit you at the moment you hit them, they change how you work for the entire day around them. we're building something called Traeco that tells you what's actually eating your limit per step so you can at least see what's burning fast vs what's fine — happy to share early access if you want to try it.
Let me choose. This common point seems more like a rationalization for the default behavior of hyperscalers. AWS isn't avoiding prepaid due to concern about my site's virality, just that prepaid = less money.
Oh please no. And the "alternatives" to API keys aren't going to help much either, they'll just add friction to getting started (as reference: see the pain involved in writing a script that hits gmail or calendar API)
i'm thinking it's time we replaced api keys.
some type of real time crypto payment maybe?