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.

Sign up for GitHub

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

Jump to bottom

Select database endpoints based on latency #3

Open
h4l opened this issue Oct 6, 2024 · 0 comments
Open

Select database endpoints based on latency #3

h4l opened this issue Oct 6, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@h4l
Copy link
Owner

h4l commented Oct 6, 2024

Right now we don't rank endpoints by latency, we just use the first one with the required consistency level. This is fine for local denokv server, but the cloud KV can provide multiple geo-located endpoints, and the spec recommends selecting based on latency:

From this list, the client MAY make requests to any endpoint, but the client SHOULD prefer endpoints that have lower latency.
@h4l h4l added the enhancement New feature or request label Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@h4l