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

smallrye-stork - Failover support #3

Open
cescoffier opened this issue Apr 5, 2022 · 1 comment
Open

smallrye-stork - Failover support #3

cescoffier opened this issue Apr 5, 2022 · 1 comment
Assignees
@aureamunoz
Labels
area/smallrye area/stork

Comments

@cescoffier
Copy link
Member

(From smallrye/smallrye-stork#232)
We had a few asks for failover support in Stork.
Currently, we stand at the position that Stork should only provide service instances and not be involved in making calls, but maybe we should revisit it?

Currently, the way to solve it is to use a failure aware load balancer, such as least-response-time and combine it e.g. with MicroProfile Fault Tolerance @Retry annotation.

upstream-organization: SmallRye
upstream-repository: smallrye-stork
upstream-issue: 232
upstream-status: open
upstream-milestone: unplanned
@cescoffier cescoffier self-assigned this Apr 5, 2022
@cescoffier cescoffier mentioned this issue Apr 5, 2022
Open
@quarkus-bot
Copy link

quarkus-bot bot commented Apr 5, 2022

/cc @Ladicek, @jmartisk, @michalszynkiewicz, @phillip-kruger, @radcortez

@gsmet gsmet transferred this issue from quarkusio/quarkus Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aureamunoz aureamunoz

Labels
area/smallrye area/stork
Projects
Quarkus Roadmap/Planning
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cescoffier @michalszynkiewicz @aureamunoz