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

connect: built-in proxy/SDK should use ?cached service discovery #4970

Open
banks opened this issue Nov 16, 2018 · 0 comments
Open

connect: built-in proxy/SDK should use ?cached service discovery #4970

banks opened this issue Nov 16, 2018 · 0 comments
Labels
theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies type/enhancement Proposed improvement or new feature

Comments

@banks
Copy link
Member

banks commented Nov 16, 2018

In 1.3.0 we added ?cached queries for service discovery. The whole reason for adding these was to enable built-in proxy (and other proxy implementations) to "fail static" such that they can still make outbound requests during a partition from the servers or server outage.

Envoy is unaffected since it requires that we "push" the results to it so it's inherently static, Using ?cached in the SDK is a trivial change that will let built-in proxy and native apps have the same behaviour without having to support full load balancing decisions locally.

@banks banks added type/enhancement Proposed improvement or new feature theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies labels Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

1 participant