paritytech / paritytech/web3-storage
Add `max_buckets` and `min_price` to `ProviderInfo`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
Based on the database research, having one db per bucket makes sense. It follows from that that the total number of buckets a provider has should be capped since they use resources different from just one bucket with a ton of storage. We should either add max_buckets or min_price or both to ProviderInfo to share some limits a provider might have that reflect its resource usage. Providers can run benchmarks in order to find values for these.
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 reading the linked database research, then locate the ProviderInfo definition and its existing uses. Determine whether max_buckets, min_price, or both should be represented based on provider resource limits; done means the selected limits are included in ProviderInfo and reflected wherever that type is consumed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100