rollupid
rollupid copied to clipboard
feat(billing): Usage based billing
Why
To support future use cases and services that inherently can scale proportionally to users' needs (eg. object storage), we need to support usage based billing.
What
- Need patterns for reporting of service usage by some consumption unit (eg. # of reads, GBs written, etc) for inclusion in a service page. In addition, need patterns for reporting the cost associated to that usage.
- Need patterns to purchase a pack of consumption units (eg. 1 million read operations) and for those to be applied to both the service usage level as well as the billing scenarios in item above.
How
- [x] Conceptual UX design or even a UX pattern for showing/managing usage based billing. We can use object storage as the illustrative example for this.