A generative API is throttled after a traffic spike.
Limit user impact and avoid a retry storm.
Choose two appropriate practices.
Use exponential backoff with jitter and define capped retries and a wait, alternate model, or human fallback.
Detailed explanation
Retries are spread out rather than synchronized.
Retries are spread out rather than synchronized.
A bounded fallback is safer than infinite retries.
A bounded fallback is safer than infinite retries.
The load and throttling worsen.
The load and throttling worsen.
Availability and quality would be misreported.
Availability and quality would be misreported.
Try it yourself
An example you can run in a temporary verification environment.
AWS公式AIF-C01 Domain 3.4とAmazon Bedrockのスロットリング・再試行設計を確認する。Expected result
再試行集中を避け、安全に利用者へ代替手段を示せる。Key points
- Backoff
- Jitter
- Fallback
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.