You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: