August 2018
Intermediate to advanced
248 pages
5h 51m
English
This pattern is recommended to alleviate the impact of identified transient failures while communicating with an external component or service, due to network failure or server overload.
Note that the retrying approach is not recommended for handling failures such as internal exceptions caused by errors in the application logic itself.
Also, we have to think about and analyze the way the external service responds. If the application experiences frequent busy faults, it's often a sign that the service being accessed has a scaling issue that should be addressed.