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

add geo routing to select closest rpc services for clients #39

Closed
smallnest opened this issue Sep 27, 2016 · 1 comment
Closed

add geo routing to select closest rpc services for clients #39

smallnest opened this issue Sep 27, 2016 · 1 comment
Labels

Comments

@smallnest
Copy link
Owner

we can get geo location based on IP addresses of services and clients. So clients can select the closest services by comparing geo locations.

It is useful because clients always select services in the same datacenter (city).

smallnest added a commit that referenced this issue Sep 29, 2016
@smallnest
Copy link
Owner Author

don't use maxmind geolite2 to implement this feature because:

  1. rpcx has been used in a company. IP addresses and geo locations of clients and servers are clear. We can set lat/lon before starting them
  2. it will take more memory to use maxmind and cache their geo db
  3. and it takes more time to query geo location from maxmind db

so this implementation uses clear latitudes and longitudes to calculate distance between clients and servers.

fireball2018 pushed a commit to club-codoon/rpcx that referenced this issue Apr 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant