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

Support for AZ awareness #165

Open
orgalaf opened this issue Apr 30, 2019 · 1 comment
Open

Support for AZ awareness #165

orgalaf opened this issue Apr 30, 2019 · 1 comment

Comments

@orgalaf
Copy link

orgalaf commented Apr 30, 2019

How about adding a feature whereby components will be able to prefer counterparts who are closer to them. For instance a requester will prefer responders in the same AZ over responders in other AZ's.

@dashersw
Copy link
Owner

This would be a great feature. In fact, cote already has an undocumented feature called subsets. If you look at requester.js code, you'll see that messages can be routed to a subset of all available responders, configured via a __subset property in the message. Likewise, responders can decide which subsets they are in via a subset property in their advertisement message. So one can set these configurations via environment variables, where an environment variable SUBSET would point to an AZ, therefore requesters would prefer this subset. The current implementation lacks one feature though — fallback. If you don't have any items in the subset, the request enqueues instead of being routed to the other responders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants