Battle of the Circuit Breakers: Resilience4J vs Istio • Nicolas Frankel • GOTO 2019

This presentation was recorded at GOTO Berlin 2019. #GOTOcon #GOTOber

Nicolas Frankel - Developer Advocate at Hazelcast

ABSTRACT
Kubernetes in general, and Istio in particular, have changed a lot the way we look at Ops-related constraints: monitoring, load-balancing, health checks, etc. Before those products became available, there were already available solutions to handle those constraints.
Among them is Resilience4J, a Java library. From the site: "Resilience4j is a fault tolerance library designed for Java8 and functional programming." In particular, Resilience4J provides an implementation of the Circuit Breaker pattern, which prevents a network or service failure from cascading to other services. But now Istio also provides the same capability.
In this talk, we will have a look at how Istio and Resilience4J implement the Circuit Breaker pattern, and what pros/cons each of [...]

Read the full abstract here:

RECOMMENDED BOOKS

#Kubernetes #k8s #Microservices #Istio #Resilience4J #Java #SoftwareArchitecture #DevOps

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[kellyfj]

You had me at "Microservices are an organizational solution to an organizational problem" - agree 10, 000%

[benyazidanass]

one of the major cons of resilience4j that he forget to mention is that resilience4j is counting failures on instance level instead of service level and opening circuit accordingly for individual instance.

[deniscapeto]

By the title I thought this video would give some insight about when to implement resilience features in a service using resilience4J and when to leave it to the side car using a service mesh. Unfortunately this was not the case.

[ariel_alves_dutra]

Hey GOTO, can you share the link of the demo source code? Thanks.