towardsthecloud / towardsthecloud/cloudburn
Estimate DynamoDB on-demand and storage costs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 371
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 63
Description
What
Estimate DynamoDB on-demand request, table storage, stream, and backup costs from explicit monthly usage assumptions.
Why
CloudBurn can price declared provisioned capacity, but on-demand tables and stored data depend on workload. Adding those inputs gives reviewers a fuller estimate without turning missing usage into zero cost.
Scope
- Price on-demand reads and writes as separate cost lines
- Estimate stored data by table class
- Include stream and backup usage only when the feature and its quantity are supplied
- Keep provisioned capacity estimates unchanged
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating CloudBurn’s existing provisioned-capacity DynamoDB pricing path and the inputs used for declared usage. Add separate on-demand read and write estimates, table-class storage estimates, and conditional stream and backup costs without changing provisioned estimates; verify each cost line against explicit monthly assumptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100