paritytech / paritytech/web3-storage
[ProviderNode] Default storage/bucket internal implementation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
Relates to: https://github.com/paritytech/web3-storage/pull/33
Currently, the provider is using an in-memory or dummy persistent disk implementation with RocksDB. A final/best solution still needs to be determined.
The protocol is provider-agnostic, but we need to have some default impl.
- How the provider physically stores data (IPFS, S3, custom, etc.)
- The provider's internal database schema or indexing
TODO
- Prepare design first (security, performance, ...) https://github.com/paritytech/web3-storage/issues/101
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 reviewing pull request 33 and the design TODO in issue 101. Compare the current in-memory or dummy persistent-disk implementation using RocksDB with the provider-agnostic storage options listed here, including IPFS, S3, and custom storage. Done means a settled design for physical storage and the internal database schema or indexing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100