Being a good client
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
behave well against someone else's limits.
Planned topics
- Read
429and honorRetry-After(seconds or a date); do not retry sooner. - Use backoff with jitter if there is no header; cap total retries.
- Respect documented limits proactively: queue and pace outbound calls.
- Batch requests and cache responses to use fewer calls.
- Log and alert on
429s you receive; they are a design signal.
Draft outline details
Demonstration
HTTP/1.1 429 Too Many Requests
Retry-After: 12Client waits at least 12 seconds, then retries.
Check your understanding
What should a client do first on a 429 with Retry-After: 12?
Show answer
Wait at least 12 seconds before retrying.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.