platform-guideline 1 linked patterns checked
Google SRE Book: Addressing Cascading Failures
Documents retry traffic as a possible positive-feedback source during failures and recommends randomized exponential backoff for scheduled retries.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Retry | Choose retry when a specific failed operation can plausibly succeed if attempted again under the same scope. | Retry repeats the same failed operation against the same request scope unless users explicitly edit that scope first. | Google SRE documents retry traffic as a possible contributor to cascading failures and recommends randomized exponential backoff. |
Comparisons supported by this source
- Retry vs error state vs loading spinner vs offline state
Google SRE documents retry amplification risk and randomized exponential backoff.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Google SRE. Last checked: .