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
We've been looking at vulcand for our environment, but we're missing some functionality that we'd like to have.
We have a pattern of falling back to a second copy of a service (in another region) before giving up, i.e. the pattern is:
try the local (read) service
if fail (using circuit breaker) try the remote (read) service
if fail -> error
Ideally, we'd handle that in the internals of vulcand, with a second backend or so, but that seems like a lot more change than necessary. We think it should be possible to make a new circuit breaker fallback using the forwarder in oxy that could do this job.
If we were to implement this, is there an appetite to accept a pull request of that nature?
The text was updated successfully, but these errors were encountered:
We've been looking at vulcand for our environment, but we're missing some functionality that we'd like to have.
We have a pattern of falling back to a second copy of a service (in another region) before giving up, i.e. the pattern is:
Ideally, we'd handle that in the internals of vulcand, with a second backend or so, but that seems like a lot more change than necessary. We think it should be possible to make a new circuit breaker fallback using the forwarder in oxy that could do this job.
If we were to implement this, is there an appetite to accept a pull request of that nature?
The text was updated successfully, but these errors were encountered: