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

Explore use of Resilience4J as a potential replacement for Hystrix #357

Closed
spericas opened this issue Jan 31, 2019 · 1 comment
Closed
Assignees
Labels
task To do

Comments

@spericas
Copy link
Member

Hystrix is in maintenance mode, we should explore Resilience4J.

@spericas spericas added the enhancement New feature or request label Jan 31, 2019
@spericas spericas self-assigned this Jan 31, 2019
@spericas spericas added task To do and removed enhancement New feature or request labels Feb 7, 2019
@spericas
Copy link
Member Author

spericas commented Feb 7, 2019

Completed the evaluation of Resilience4J:

  • Inspired by Hystrix
  • Functional model very different from Hystrix
  • Could potentially replace FailSafe as well
  • Better circuit breaker support
  • Given the differences, not a drop-in replacement for Hystrix

Although technically possible, using Resilience4J would basically require a complete re-write of some parts of our FT implementation. We should keep this in mind when scheduling a task for this.

@spericas spericas closed this as completed Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task To do
Projects
None yet
Development

No branches or pull requests

1 participant