How To Integrate Circuit Breaker And Retry In A Spring Boot Application Using Resilience4J

In this video, we will be exploring how to integrate Resilience4J Circuit breaker and Retry mechanism in a Spring Boot Application.
Here we look into how the circuit breaker moves from OPEN state to HALF_OPEN and then back to the OPEN state.
You can also read about this along with the GitHub link to the code: refactorfirst.com/spring-clou...
You can support me by buying me a coffee 😄 : www.buymeacoffee.com/amrutprabhu
Gear I use:
Sony Alpha a6000 : Amazon India : amzn.to/3RM7QMJ
Germany : amzn.to/3G1Iw24
US : amzn.to/3cpKZ9E
UK : amzn.to/3J0g5Ry
Razer Microphone : Amazon India : amzn.to/3aQxI9C
Germany : amzn.to/3DRRrAh
US : amzn.to/3ITKu3Q
UK : amzn.to/3v3RHbU
------Chapters----
00:00 - Introduction
00:47 - Creating An Application
01:18 - Code Walkthrough
01:35 - Retry Annotation
02:27 - Understanding Retry Config Properties
03:52 - Spring Aspect Dependency
04:33 - Starting Application
05:00 - Retry Output
05:31 - Adding circuit Breaker
06:11 - Understanding Circuit Breaker Configuration
08:00 - Understanding HALF_OPEN state
08:38 - Starting The Application
09:00 - Circuit Breaker & Retry Aspect Order
09:55 - Changing Circuit Breaker & Retry Order
10:30 - Starting application with new Order
11:09 - Evaluating Circuit Breaker With Retry
11:29 - Circuit Breaker in OPEN state
12:00 - OPEN to HALF_OPEN State
12:45 - HALF_OPEN To OPEN State
13:09 - Conclusion
Music Credits:-
Sappheiros - Promise
----------------------------
Social Media
CZcams / sappheiros
Spotify goo.gl/hE9MDJ
Twitter SappheirosMusic
Instagram sappheirosmusic
Facebook SappheirosMusic
Discord discord.gg/Pk87yN9
/ promise
--------------------------------------------------

[@secondchance021]

I found this video very useful, especially the part to use the patterns complimenting each other.

[@thavadaboinabhuvaneshwar9581]

Thank you for clarifying the complex concepts, I am clearly understood the concept, keep posting videos 👍

[@progKev]

Thank you for this video. Finding information on using a Retry and a CircuitBreaker together is tough. Thank you for doing a video on this topic.

[@Emerald214]

Subscribed. Thanks for the useful information that not many articles have.

[@OlegPetrow-ze6ft]

Thank you for this video!

[@shaziyahasan7775]

Thanks for the great explanation💯

[@krishnavardhandasari2694]

Thanks very much sir for making things clear and easy.

[@pranavmahajan4190]

Mitra ekadam mast tutorial aahe. Thanks

[@ferdinandodemelo2222]

Excellent explanation

[@srinivasshiva5]

Thanks for the help and this is working for me also very helpfull to my project. Thanks once again..

[@kumarpushkar6621]

Very clear and accurate information, keep it up!

[@RefactorFirst]

Thanks a lot.. more interesting stuffs on the way..

[@zhimengjin7373]

Great video, handsome boy 😃

[@sivakoti9799]

Nice presentation

[@GautamKumar-dg8qc]

Thanks for this good content.
I have one doubt, suppose in your case each retry is making 3 calls to the server, but this 3 is counted 1 as one for the circuitbreaker, what if I wanted to count the retries also in the circuitbreaker.
means one call = 3 retries = 3 failurecall in circuitbreaker.

[@andresweitzel.archivo3521]

Excellent explanation, I have seen that it is not common to work with paging in resilience, the question is, if you have some microservices applying paging... if I return a list or a String through the resilience endpoint... what would be the logic of use pagination...? ... the idea is to have a cleaner and safer code from the resilience service, but if I apply paging I am practically developing the same microservice that implements it....

[@shakilahmed4647]

Hi. you are doing good. Please keep making new ones.

[@RefactorFirst]

Thanks a lot for feedback.. really appreciate it.. more coming soon.

[@niharchauhan7450]

Thank you for such clear explanation. I have one query.
If the minimum number of calls is set to 5 and failure rate threshold is 60%. Then ideally circuit breaker should be open after 3 calls only because 60% of 5 = 3. Then why circuit breaker didn’t open after 3 calls and only after 5 calls?
Hoping for a response.
Thanks !!

[@RefactorFirst]

Yes.. this concept can confuse everyone.
What it actually means is, it considers minimum 5 calls to kick off the evaluation. And if the evaluation results in 60% of the calls failed, then the circuit breaker opens.
So if 3 out of 5 fails then the circuit breaker opens.

[@rexsam3134]

Did you migrate to latest Spring Boot version 3.1.5?

[@sagar0rohankar]

मस्त रे माझ्या जोश लाँग

[@RefactorFirst]

Tumchyach krupe ni .. :)

[@mahas.h.4024]

Thanks a lot. Question - is it possible to use retry module when circuit breaker is closed?

[@RefactorFirst]

Yes.. that the reason, the retry has been given a higher priority..

[@sreedevimasarapu6214]

Hi Sir,
This vedio is very usefull for learners and in my project i have same requirement to implement circutbreaker.
I followed all steps which you are mentioned but it not working.
1. added these all jars resilience4j-reactor,resilience4j-circuitbreaker,resilience4j-core,resilience4j-all,resilience4j-annotations.
2. Added these properties
resilience4j.circuitbreaker.instances.cartValidationFromErp.registerHealthIndicator =true
resilience4j.circuitbreaker.instances.cartValidationFromErp.failureRateThreshold=50
resilience4j.circuitbreaker.instances.cartValidationFromErp.slidingWindowSize=10
resilience4j.circuitbreaker.instances.cartValidationFromErp.slidingWindowType=COUNT_BASED
resilience4j.circuitbreaker.instances.cartValidationFromErp.minimumNumberOfCalls=5
resilience4j.circuitbreaker.instances.cartValidationFromErp.automaticTransitionFromOpenToHalfOpenEnabled=true
resilience4j.circuitbreaker.instances.cartValidationFromErp.permittedNumberOfCallsInHalfOpenState=4
resilience4j.circuitbreaker.instances.cartValidationFromErp.waitDurationInOpenState=5s
3.Added @CircuitBreaker(name="cartValidationFromErp") in service class method level
With out my above changes response is coming but with above changes response not coming and not throwing any exception.