Fault Tolerance is a Requirement Not a Feature - Adar Danait, Lilian Ernest, Citi

December 14, 2017
The application ecosystem for our business consists of 700+ services. A typical transaction request flows through 5+ service instances before its processed. In this distributed environment, inevitably some of the many service dependencies will fail. Each dependent service invocation is costly and a single failure can lead to diminished user experience and a lower Net Promoter Score for us either on the mobile app or desktop. It also places a higher stress on the underlying system that is attempting to recover from the failure. We use Hystrix as a fault tolerance open source framework provided by Netflix designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable. During this session you will learn: Hystrix Circuit breaker mechanism How to use Hystrix in microservices Hystrix best practices and recommendations Slides: TBA Adar Danait, Principal Software Engineer, Citi Lilian Ernest, Apps Dev Tech Specialist, Citi Filmed at SpringOne Platform 2017
Previous
Managing the Complexity of Microservices Deployments - Prithpal Bhogill, Kenny Bastani
Managing the Complexity of Microservices Deployments - Prithpal Bhogill, Kenny Bastani

To rapidly deliver microservices to production, organizations are turning to infrastructure automation prov...

Next Video
Cloud Foundry UAA as an Identity Gateway - Sree Tummidi
Cloud Foundry UAA as an Identity Gateway - Sree Tummidi

In this session we will cover the capabilities of Cloud Foundry’s UAA which make it apt to be used as an id...