Create better client behavior can make your system become more reliable.

1. Build a better client
Improve reliability and resilience

2. Fallacies of distributed computing

3. 1. The network is reliable.
2. Latency is zero.
3. Bandwidth is infinite.
4. The network is secure.
5. Topology doesn't change.
6. There is one administrator.
7. Transport cost is zero.
8. The network is homogeneous.
https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing

4. Reliability matters

5. How are we gonna improve reliability and
reduce operational cost for the developer

6. 7 resilience policies we can adopt

7. 1. Retry
Overcome transient failures

8. ● Failure that retry might help
■ DNS error
■ Connection error
■ Timeout
● When to retry
■ 503 (Service unavailable)
■ 429 (too many requests)
■ 408 (request timeout)
■ 500 (Internal server error) DON”T continually retry
○ Receive 400, fix your input data

9. 2. Retry + Back off + Jitter
Protecting failing server from overload

10. https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/

11. 3. Circuit Breaker
Fail fast and stop hurting other services

13. 4. Timeout
Don’t wait forever

14. 5. Cache
You have asked that one before

15. 6. Bulkhead isolation
One fault should sink the whole ship

16. https://dzone.com/articles/performance-patterns-in-microservices-based-integr-1

17. https://dzone.com/articles/performance-patterns-in-microservices-based-integr-1

18. 7. Fallback
Return alternative response while failure