Spring Tips: Spring Cloud Circuit Breaker

[@thenylon1003]

Thanks for the video! May I ask - what are the proper generic parameters for the factory? I get a warning: Raw use of parameterized class 'ReactiveCircuitBreakerFactory' Thank you!

[@mohammedaayachi3828]

Crystal clear as usual, Thanks Josh.

[@gurucharansharma5574]

What is the difference between the above approach and annotation approach, where we use @CircuitBreaker annotation. Annotation approach is much more customizable. We can specify various properties and attributes through the YML or properties file. Which one to use when? Would you please elaborate on this a little but more?

[@gialnetantonio]

Really nice, Thanks Josh

[@prakashb2669]

Great video as usual, this is a great project from Spring, since this is a abstraction over other circuit breakers, I presume it'll be helpful to migrate from one implementation to another. And, there're few grudges in Hystrix Circuit Breaker like 1) Most of the time developers not using the "right" thread pool configurations. I wish we have some opinionated settings based on requests per second. 2) Sometimes circuits are opened for bad requests though it's ignored. I don't know if this project will help alleviate/solve some of these problems. Will see - thanks!

[@monikasoodin]

Hi Josh, Very nice video but I m missing something here and cannt import the dependency spring-cloud-starter-circuitbreaker-resilence4j. Can you please specify what repository are you using.

[@jorgetovar621]

This implementation is based on resilence4j or hystrix?

[@FabioEbner]

please create one video to how secure REST API with keycloak. tks

[@AdrianoKretschmer]

I didn't know Circuit Braker was elaborated Exception Treatment.

[@fahdfprime3314]

Who can explain with simple words what a circuit breaker is ? Thanks

[@ToonBorgers]

It's a pattern to handle 'faulty' behavior, usually when calling some external system. You can define what 'faulty' means (service unavailable, timeout, a certain exception) and handle this gracefully (like returning a default or some other fallback) instead of having the error propagate and crash your system

[@fahdfprime3314]

Toon Borgers if it is just what you have described I call it in my world error/fault handling 😂 Thanks you a lot really 🙏🏾

[@robertwinkler9934]

@@fahdfprime3314 you can read this resilience4j.github.io/resilience4j/#_circuitbreaker_14

[@zoli11]

yes, because the explanation is wrong. A circuit breaker is used to stop hitting on a service that is known to be in a faulty state. The idea being that a) it further overwhelms the faulty system, even once it would start to recover, b) waiting for non-responding services for several seconds is pointless. Instead the circuit breaker short-cuts with an error response without even asking the external service, once it knows that the external service is faulty. However it does let through a request periodically to probe if the service has maybe recovered. If it gets good responses, it reopens.

[@NastyaSmirnova]

martinfowler.com/bliki/CircuitBreaker.html

[@behzadkhosrojerdi3315]

👌👍

[@luisdanielmesa]

we already have microprofile in javaEE

[@MrKiraBR]

Amazing content. But seeing this two spaces (or one) identation, kind hurts...

[@kanadsante225]

This video should be renamed as "Reactive" Spring Cloud Circuit Breaker. As there are lot of reactive concepts used and focus get shifted from circuit breaker to Reactive.