5 ms·
I'm with you on the first part, but not the second (ha). Time-based billing should be granular to the second/minute/hour depending on the service, but should b
by unethical_ban 6y ago
I'm with you on the first part, but not the second (ha).
Time-based billing should be granular to the second/minute/hour depending on the service, but should be listed for the customer in a table upwards an order of magnitude or so.
VM instances often get turned up and down in less than an hour. Serverless functions (AWS Lambda) execute and then end in milliseconds, often.
But yes, billing should be simpler/more clearly reported and calculated. And many of their services seem to bill in overly complicated ways.
On the other hand, I think some AWS services are essentially free for small amounts of usage, so individuals have less to worry about re: billing.
- systemvoltage 6y ago> Time-based billing should be granular to the second/minute/hour depending on the service, but should be listed for the customer in a table upwards an order of magnitude or so. That's what I meant by "Billing can happen in microunits". You described it better.