Spring Boot Microservices Project Example - Part 6 | Resilience4J Circuit Breaker

Spring Boot Microservices Project Example - Part 6 | Resilience4J Circuit Breaker
Source Code
github.com/SaiUpadhyayula/spr...
⭐️⭐️ You can follow me on Social Media through the below Links⭐️⭐️
Twitter: / sai90_u
Blog: programmingtechie.com/
Dev.to: dev.to/saiupadhyayula
Facebook Page: / programmingtechie

[@defrankline]

Thanks bro! your tutorial are simple to follow and cover what its needed!

[@toto_frs620]

I love your videos. Well done!

[@diggydavro1588]

Great tutorial 👌 easy to follow keepnthe good work

[@vaishnavepranav7394]

Thanks for the wonderful tuorial .

[@hoangtv3949]

Very useful

[@user-cf7bi1tx1h]

Thank you so much :) _/\_ Highly appreciated!

[@vietnguyenba4680]

Thanks, bro! You can share videos about managing transactions in a microservice system.

[@adityamankar9543]

Thank you for these amazing tutorials. Can you please add a video demonstrating the deployment process for microservices?

[@defrankline]

i second this. at the end lets deploy this app using say docker, kubernetes

[@deanclancy6448]

Yes please🙏🙏

[@ProgrammingTechie]

It's already in plan to integrate the project to Kubernetes.

[@exploreWorldMe1984]

Thanks! wonderful tutorial... keep up the good work

[@ProgrammingTechie]

Thank you

[@az910]

Thank you 🙏 When you will share the next part ? Haha 😁

[@ProgrammingTechie]

On Tuesday :)

[@az910]

I appreciate what you do for us

[@manojkumar8358]

@@ProgrammingTechie Please tell on how to add junit test case for fallback method

[@osasereuhunmwangho5293]

Hello Programming Techie. I am facing an issue with the time-out exception. I want to keep the logic stuff in the service and the controller stuff strictly in the controller. Do I have to move my logic to the controller before a time-limiter exception is thrown? I don't think so. The annotations i.e. CircuitBreaker, TimeLimiter are in the service layer. I am returning a type of CompletableFuture in the service layer also. The controller attached to it is also returning a type of CompletableFuture. The error observed when I run in postman is that, TimeLimiter annotation ought to return a type of CompletionStage which means the service should have a return type of CompletionStage instead of CompletableFuture. Once this is done, I have tried using a return type of CompletionStage in the controller too. On the other hand, I have used a return type of CompletableFuture and I simply cast the response of the service to CompletionStage. Either way, the time-out exception is not being thrown when I try to send in Postman. All it does is wait for as long as the thread.sleep is set in the inventory service. After which, the order is then successfully placed. Please what is the way around it?

[@osasereuhunmwangho5293]

I have found a way around it. I simply moved the @TimeLimter annotation to the controller. The circuit breaker annotation remains in the service. The service returns a type of String while the controller returns a CompletableFuture

[@NoOne-mg6ti]

@@osasereuhunmwangho5293 I'm also having the same problem. Can you show me your code on handling this problem?

[@yogeez123]

If you are using Gateway and service to service communication should be done through gateway, I believe

[@ProgrammingTechie]

Gateway acts as an entrypoint of a request into our system, from there the request is routed through other services, internal service to service communication is not done through API Gateway.

[@nonamespls3468]

why didn't the fallback work when timeout was thrown?

[@kevinm.1597]

Thank you for this tutorial! but i am facing an issue right now TimeLimiter is not throwing the TimeoutException

[@KK-wu2fq]

Programming Techie any idea why?

[@KK-wu2fq]

ive been doing CB stuff on service, i moved all to controler and there it throws exception for timelimiter :)

[@osasereuhunmwangho5293]

@@KK-wu2fqHello. I am facing the same issue. I want to keep the logic stuff in the service and the controller stuff strictly in the controller. Do i have to move my logic to the controller before a timelimiter exception is thrown. Did you find a way around it?

[@osasereuhunmwangho5293]

I have found a way around it. I simply moved the @TimeLimter annotation to the controller. The circuit breaker annotation remains in the service. The service returns a type of String while the controller returns a CompletableFuture

[@razataggarwal7365]

Circuit Breaker annotation doesn't work for java 1.8 but why ?

[@abhinandankumar4255]

next video please

[@QuickInterviewPrep]

Great tutorial :). can we implement circuit breaker in gateway? Or As my UI is calling gateway and gateway is calling my service, should i implement in UI(say react)

[@ProgrammingTechie]

Yes you can also implement it in the gateway

[@QuickInterviewPrep]

@@ProgrammingTechie Not sure if we can implement it in gateway as gateway is just routing not making rest call. Did i understand correctly? In your example you implemented it method that is calling rest endpoint

[@ognjenbarovic1756]

Is it just me or orderRepository still saves order after timeout?

[@baranemreturkmen9497]

Yeah me too. And I don't understand why

[@baranemreturkmen9497]

In my problem I relaized that I didn't invoke my placeOrder method which in OrderService class, with resilience4j time limiter. Maybe you did same mistake with me.

[@aamirshaikh1389]

I'm currently dealing with a similar problem, and I'd appreciate it if you could share more details on how you resolved the issue? @@baranemreturkmen9497

[@bautistaquesada4436]

Hey! can someone help me please im having this issue An expected CSRF token cannot be found, when im trying to do a post in localhost:8080/api/order, i dont know how to solve it my application.properties of my discovery server is the same as the video. so i dont understand what is happening

[@ProgrammingTechie]

Please cross check the code against the GitHub repo

[@bautistaquesada4436]

@@ProgrammingTechie Hi! yes i double check with the repo and the problem persist.

[@user-lz7wx7dg5f]

My status always shows closed. never Open or even half open. Not sure why

[@king0s]

Bring the other service down?

[@vishalwagh478]

I too have a similar problem. Because the circuit breaker was not registering itself. Hence I changed the resilience4j.circuitbreaker.instances.inventory.registerHealthIndicator => resilience4j.circuitbreaker.instances.default.registerHealthIndicator Hence even though inventory was down, the circuit breaker was not identified & state was in OPEN state only. After reverting back to circuit status was started reflecting correctly.