No Retry vs Retry Pattern
Developers should learn and apply No Retry in scenarios where retries could lead to worse outcomes, such as in microservices architectures, database operations, or external API calls where failures might be persistent or indicative of deeper issues meets developers should use the retry pattern when building distributed systems or applications that rely on external services, apis, or databases, where transient failures are common and can resolve on their own. Here's our take.
No Retry
Developers should learn and apply No Retry in scenarios where retries could lead to worse outcomes, such as in microservices architectures, database operations, or external API calls where failures might be persistent or indicative of deeper issues
No Retry
Nice PickDevelopers should learn and apply No Retry in scenarios where retries could lead to worse outcomes, such as in microservices architectures, database operations, or external API calls where failures might be persistent or indicative of deeper issues
Pros
- +It is crucial for building robust systems that avoid amplifying transient errors into system-wide outages, and it aligns with practices like graceful degradation and observability-driven error management
- +Related to: circuit-breaker, error-handling
Cons
- -Specific tradeoffs depend on your use case
Retry Pattern
Developers should use the Retry Pattern when building distributed systems or applications that rely on external services, APIs, or databases, where transient failures are common and can resolve on their own
Pros
- +It is essential for improving fault tolerance in microservices architectures, cloud-based applications, and IoT systems, ensuring that temporary glitches don't cause unnecessary user-facing errors
- +Related to: circuit-breaker-pattern, resilience-patterns
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use No Retry if: You want it is crucial for building robust systems that avoid amplifying transient errors into system-wide outages, and it aligns with practices like graceful degradation and observability-driven error management and can live with specific tradeoffs depend on your use case.
Use Retry Pattern if: You prioritize it is essential for improving fault tolerance in microservices architectures, cloud-based applications, and iot systems, ensuring that temporary glitches don't cause unnecessary user-facing errors over what No Retry offers.
Developers should learn and apply No Retry in scenarios where retries could lead to worse outcomes, such as in microservices architectures, database operations, or external API calls where failures might be persistent or indicative of deeper issues
Disagree with our pick? nice@nicepick.dev