In these situations, it might be pointless for an application to continually retry an operation that's unlikely to succeed. These faults can range in severity from a partial loss of connectivity to the complete failure of a service. However, there can also be situations where faults are due to unanticipated events that might take much longer to fix. These faults typically correct themselves after a short time, and a robust cloud application should be prepared to handle them by using a strategy like the "Retry pattern". In a distributed environment, calls to remote resources and services can fail due to transient faults, such as slow network connections and timeouts, or if resources are responding slowly or are temporarily unavailable. Handling this type of fault can improve the stability and resiliency of an application.
As noted earlier, you should handle faults that might take a variable amount of time to recover from, as might happen when you try to connect to a remote service or resource.
0 kommentar(er)
