Speaker
Until conference starts:
✓ Team discounts
✓ All inclusive 4-Day Passes available
Until conference starts:
✓ Team discounts
✓ All inclusive 4-Day Passes available
Infos
16:00 - 16:45
Studio 3
Description
Distributed systems should definitely no longer be developed and operated without resilience. The responsible developer or architect must first consider which resilience patterns are necessary. The next question is how the implementation of these patterns in the individual services should take place. One can distinguish between two basic alternatives. On the one hand an implementation with the classic resilience frameworks such as Resilience4J, Failsafe or MicroProfile Fault Tolerance. On the other hand, it is also possible to establish resilience with a service mesh tool like Istio.
In this session, after a brief introduction to Istio, the two basic alternatives are compared. The respective advantages and disadvantages are listed and compared in a final evaluation. Additional possibilities of Istio to explicitly test resilience will also be introduced.
This Session belongs to the Diese Session gehört zum Programm vom MunichMünchen program. Take me to the program of . Hier geht es zum Programm von London London .
This Session belongs to the Diese Session gehört zum Programm vom MunichMünchen program. Take me to the program of . Hier geht es zum Programm von Berlin Berlin .
This Session belongs to the Diese Session gehört zum Programm vom MunichMünchen program. Take me to the program of . Hier geht es zum Programm von New York New York .