Skip to content
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

feat: Autosharding API for req-resp protocols #673

Closed
2 tasks done
chair28980 opened this issue Aug 23, 2023 · 2 comments
Closed
2 tasks done

feat: Autosharding API for req-resp protocols #673

chair28980 opened this issue Aug 23, 2023 · 2 comments
Assignees
Labels
E:1.2: Autosharding for autoscaling See https://github.com/waku-org/pm/issues/65 for details

Comments

@chair28980
Copy link
Contributor

chair28980 commented Aug 23, 2023

This tracks the work necessary in each client to provide API(s) to applications using req-resp protocols (store, lightpush, filter, etc.) with optional pubsub topic arguments. Each client should then use autosharding to determine the associated shards on behalf of applications. Note that underlying protocols should not be affected and each client implementation should locally populate pubsub topic fields with the shards hashed from content topics received via the API.

Priority: Critical for launch

Tasks

@chaitanyaprem chaitanyaprem added E:1.2: Autosharding for autoscaling See https://github.com/waku-org/pm/issues/65 for details and removed E:2023-1mil-users labels Sep 11, 2023
@chaitanyaprem
Copy link
Collaborator

Weekly Update

  • achieved: Completed Filter API and lightClient changes for autosharding

@chaitanyaprem
Copy link
Collaborator

Weekly Update

  • achieved: Updated lightpush API for autosharding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:1.2: Autosharding for autoscaling See https://github.com/waku-org/pm/issues/65 for details
Projects
Archived in project
Development

No branches or pull requests

2 participants