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

HTTP Based Discovery as an alternative to MultiAddress #134

Open
luongngocminh opened this issue Feb 15, 2024 · 0 comments
Open

HTTP Based Discovery as an alternative to MultiAddress #134

luongngocminh opened this issue Feb 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@luongngocminh
Copy link
Contributor

In the current state, in order to initialize a cluster, a seed in a form of a multiaddr will be required. This seed can only be decided when there're at least 1 node already running (unpredictable port and ip addresses). Due to this limitation, we cannot seamlessly spin up a cluster without having some overhead logic for acquiring the initial seed.
So instead of using multiaddr explicitly, we can opt for an HTTP Based Discovery using API Endpoints somehow.

@luongngocminh luongngocminh added the enhancement New feature or request label Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant