Is really necessary to use Hystrix with reactive spring boot 2 application?












1















I'm working in a project in which we are moving some of ours microservices from Spring-MVC to Spring-Webflux to test the reactive paradigm. Looking for some help in the github repository of hystrix we've noted that the project have no commits since a year ago, and it's based in RxJava, so there are some incompatibilities with project-reactor.



We're having some issues using Hystrix, particulary that the annotations from "Javanica" doesn't work and our developers need to use HystrixCommands from Spring-Cloud instead. And the fact that Hystrix, obviously, creates his own pool of threads aside from the ones of reactor.



Reached this point my question is not how to use Hystrix with Spring Boot 2.0 but if it's a must to wrap all the external calls from our microservices in an HystrixCommand or if simply using the Reactor methods (timeout, onError, retry, etc.) we can avoid this wrapping.










share|improve this question



























    1















    I'm working in a project in which we are moving some of ours microservices from Spring-MVC to Spring-Webflux to test the reactive paradigm. Looking for some help in the github repository of hystrix we've noted that the project have no commits since a year ago, and it's based in RxJava, so there are some incompatibilities with project-reactor.



    We're having some issues using Hystrix, particulary that the annotations from "Javanica" doesn't work and our developers need to use HystrixCommands from Spring-Cloud instead. And the fact that Hystrix, obviously, creates his own pool of threads aside from the ones of reactor.



    Reached this point my question is not how to use Hystrix with Spring Boot 2.0 but if it's a must to wrap all the external calls from our microservices in an HystrixCommand or if simply using the Reactor methods (timeout, onError, retry, etc.) we can avoid this wrapping.










    share|improve this question

























      1












      1








      1


      2






      I'm working in a project in which we are moving some of ours microservices from Spring-MVC to Spring-Webflux to test the reactive paradigm. Looking for some help in the github repository of hystrix we've noted that the project have no commits since a year ago, and it's based in RxJava, so there are some incompatibilities with project-reactor.



      We're having some issues using Hystrix, particulary that the annotations from "Javanica" doesn't work and our developers need to use HystrixCommands from Spring-Cloud instead. And the fact that Hystrix, obviously, creates his own pool of threads aside from the ones of reactor.



      Reached this point my question is not how to use Hystrix with Spring Boot 2.0 but if it's a must to wrap all the external calls from our microservices in an HystrixCommand or if simply using the Reactor methods (timeout, onError, retry, etc.) we can avoid this wrapping.










      share|improve this question














      I'm working in a project in which we are moving some of ours microservices from Spring-MVC to Spring-Webflux to test the reactive paradigm. Looking for some help in the github repository of hystrix we've noted that the project have no commits since a year ago, and it's based in RxJava, so there are some incompatibilities with project-reactor.



      We're having some issues using Hystrix, particulary that the annotations from "Javanica" doesn't work and our developers need to use HystrixCommands from Spring-Cloud instead. And the fact that Hystrix, obviously, creates his own pool of threads aside from the ones of reactor.



      Reached this point my question is not how to use Hystrix with Spring Boot 2.0 but if it's a must to wrap all the external calls from our microservices in an HystrixCommand or if simply using the Reactor methods (timeout, onError, retry, etc.) we can avoid this wrapping.







      spring spring-boot spring-webflux project-reactor hystrix






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 13:45









      david.delamodavid.delamo

      184




      184
























          1 Answer
          1






          active

          oldest

          votes


















          1














          You could replace many of hystrix features with built-in Reactor methods (timeout, retry, limitRate, onError...).



          For circuit breaker you could use Resilience4j. It is easy to embed it into existent Reactor code



          Mono<MyClass> myMono = ...;
          CircuitBreaker circuitBreaker = ...;
          myMono.transform(CircuitBreakerOperator.of(circuitBreaker)).subscribe(...)





          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53282413%2fis-really-necessary-to-use-hystrix-with-reactive-spring-boot-2-application%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            You could replace many of hystrix features with built-in Reactor methods (timeout, retry, limitRate, onError...).



            For circuit breaker you could use Resilience4j. It is easy to embed it into existent Reactor code



            Mono<MyClass> myMono = ...;
            CircuitBreaker circuitBreaker = ...;
            myMono.transform(CircuitBreakerOperator.of(circuitBreaker)).subscribe(...)





            share|improve this answer




























              1














              You could replace many of hystrix features with built-in Reactor methods (timeout, retry, limitRate, onError...).



              For circuit breaker you could use Resilience4j. It is easy to embed it into existent Reactor code



              Mono<MyClass> myMono = ...;
              CircuitBreaker circuitBreaker = ...;
              myMono.transform(CircuitBreakerOperator.of(circuitBreaker)).subscribe(...)





              share|improve this answer


























                1












                1








                1







                You could replace many of hystrix features with built-in Reactor methods (timeout, retry, limitRate, onError...).



                For circuit breaker you could use Resilience4j. It is easy to embed it into existent Reactor code



                Mono<MyClass> myMono = ...;
                CircuitBreaker circuitBreaker = ...;
                myMono.transform(CircuitBreakerOperator.of(circuitBreaker)).subscribe(...)





                share|improve this answer













                You could replace many of hystrix features with built-in Reactor methods (timeout, retry, limitRate, onError...).



                For circuit breaker you could use Resilience4j. It is easy to embed it into existent Reactor code



                Mono<MyClass> myMono = ...;
                CircuitBreaker circuitBreaker = ...;
                myMono.transform(CircuitBreakerOperator.of(circuitBreaker)).subscribe(...)






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 14 '18 at 15:14









                Alexander PankinAlexander Pankin

                64126




                64126






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53282413%2fis-really-necessary-to-use-hystrix-with-reactive-spring-boot-2-application%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Bressuire

                    Vorschmack

                    Quarantine