Spring / Resilience4j Interview questions
Why is Resilience4j often preferred over Hystrix?
Hystrix was put into maintenance mode by Netflix in 2018, so Resilience4j is preferred today largely because it's the actively maintained option, with regular releases and support for current Java versions and frameworks that Hystrix never received.
Architecturally, Resilience4j is built on plain functional interfaces and requires no mandatory RxJava dependency, whereas Hystrix's command-based model pulled in RxJava and forced a heavier, class-per-call style even for simple synchronous calls.
Resilience4j is also modular - a project can add just resilience4j-retry without pulling in circuit breaking, rate limiting, or bulkheading it doesn't need - while Hystrix bundled its patterns together with fewer options to opt out individually.
Its native Micrometer integration also fits more naturally into a modern Spring Boot observability stack than Hystrix's own dashboard and metrics stream ever did.
More Related questions...