-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] 1.2: Autosharding for autoscaling #65
Comments
Work completed in nwaku (minus a non-critical feature). |
Weekly Update
|
Work completed in go-waku. |
Unknown: How to handle prioritizing js-waku remaining issues in this epic. |
@chair28980 find the relevant issues for the following PRs and add to epic description: waku-org/nwaku#1854 Issue to add: |
waku-org/js-waku#1775 -- Removed from 1.2 Epic. |
Summary
This epic tracks designing and implementing an autosharding strategy based on content topics and the design requirements established in 1.1. The first phase would likely be to launch with a limited number of shards (perhaps no more than 128?). More shards can be added as the network grows organically, perhaps using some "generation ID", that allows opening more shards with successive generations.
Acceptance Criteria
Tasks
Non-critical enhancements:
The text was updated successfully, but these errors were encountered: