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

Use libp2p or Raft to distribute location information about a specific artifact #7

Open
sunsided opened this issue Jun 16, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@sunsided
Copy link
Member

Instead of encoding the source information (e.g. pod IP) of a specific artifact in the artifact's ID, libp2p, Raft, some gossip protocol could be used to proactively distribute the info. This way any participating service may know the artifact even before it is fully uploaded on the source and services may decide to use near caching if available.

Near Caching

For example, if service A and B both require information from the source, service A pulled the information before service B could and they share the same IP, then service B could decide to request the file from service A instead of the origin. This could lead to reduced latency and cost saving due to reduced inter-zone traffic.

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