PYA-9617 Resilient service-to-service calls in a post-Hystrix world | Devoxx

Devoxx Poland 2019
from Monday 24 June to Wednesday 26 June 2019.

   Resilient service-to-service calls in a post-Hystrix world

Conference

Server Side Java
Server Side Java
Intermediate level

At N26, we want to make sure that we have resilience and fault tolerance built into our backend service-to-service calls. Most of our services have been using a combination of Hystrix, Retrofit, Retryer, and other tools towards achieving this goal. However, given the latest announcement from Netflix that Hystrix is no longer under active development, we needed to come up with a replacement solution that maintains the same level of functionality. Furthermore, because Hystrix provided a big portion of our http client resilience (including circuit breaking, connection thread pool thresholds, easy to add fallbacks, response caching, etc.), we wanted to treat its deprecation as a good opportunity to revisit our entire http client resilience stack and see if we can propose a solution that consolidates our fragmented tooling into an easy-to-use and consistent approach.

Circuit Breaker   resilience   MicroServices   service mesh   retries  
Subscribe to Devoxx on YouTube
Rares Musina
Rares Musina
From N26

Rareş has been working in N26 as a Senior Software Engineer and aspiring Tech Lead for around 2 years. That’s ages in startup time and it has pushed him to cover a wide range of teams, roles and responsibilities. Before that he has held various engineering roles in Microsoft’s Skype division, where he was making sure people can login and register at scale. He’s known to be really bad at thumb wrestling.


Sign-in
Make sure to download the Android or iOS mobile schedule.