Link to the written tutorial: programmingtechie.com/2024/05/26/spring-boot-microservices-tutorial-part-6/

Finally!!! Tons of thanks

Resilience4j is a lightweight fault tolerance library inspired by Netflix Hystrix, but designed for functional programming. Resilience4j provides higher-order functions (decorators) to enhance any functional interface, lambda expression or method reference with a Circuit Breaker, Rate Limiter, Retry or Bulkhead. You can stack more than one decorator on any functional interface, lambda expression or method reference. The advantage is that you have the choice to select the decorators you need and nothing else.

Thank you so much!

HI Sai, in earlier video you have used the Feign client. But in this video the implementation is of RestClient

can you make a video about integerating service discovery with gateway mvc ?

Sai, No doubt your video contains quality but if you want real deal in KZfaq, Pls add angular as frontend as well. May be it attracts masses due to output are visible in screen, or may be demand of full stack is on high. And videos are coming too late to adhere.. speed up buddy. I know you're working fellow & editing takes time, but you've potential to become one of the top project based youtuber.

Please upload videos speedly

My all services are UP but then also fallback is getting called. I just created separate RestControllers for all service fallbacks and I also passing their URI correctly. Any solution? My Application.yml configurations for resilience4j : # Actuator endpoints management: health: circuitbreakers: enabled: true endpoints: web: exposure: include: - "*" endpoint: health: show-details: always # Resilinece4j Properties resilience4j: circuitbreaker: configs: default: registerHealthIndicator: true slidingWindowType: COUNT_BASED slidingWindowSize: 10 failureRateThreshold: 50 waitDurationInOpenState: 5s permittedNumberOfCallsInHalfOpenState: 3 automaticTransitionFromOpenToHalfOpenEnabled: true minimumNumberOfCalls: 5 timelimiter: configs: default: timeoutDuration: 3s retry: configs: default: maxAttempts: 3 waitDuration: 2s

Good evening

21:05 Either of the two should be sufficient (logically thinking), I guess: resilience4j.circuitbreaker.configs.default.failureRateThreshold=50 resilience4j.circuitbreaker.configs.default.minimum-number-of-calls=5 Then why the circuit breaker configuration requires these both to be specified along with: resilience4j.circuitbreaker.configs.default.slidingWindowSize=10 I mean: What would be the behaviour of the setup when: minimum-number-of-calls=6, failureRateThreshold=40, and slidingWindowSize=10 ??

One question, please? Do we still need this Circuit Breaker if we already have service discovery? thanks.

Let say I run more than one product services. How the gateway knows how many product services are actually available?

Please release next video