Client resilience patterns in Microservices
A client consumes remote resources through servers with no expectation of errors or any performance drawbacks in common cases. What it should do if errors happen or in case of poor performance? How we should resolve these problems when a client needs a resource and tries to retreive it iteratively but each attempt ended in failure? Answers can be hidden in resiliency patterns: Client-side load balancing Circuit breakers Fallbacks Bulkheads Client-side load balancing A client defines a destination of request routing by having information about service’s instances, their physical location....