Module 5 of 6Lesson 1 of 3~15 min
Pagination and rate limits
An integration that works on ten rows can break on ten thousand. This lesson teaches you to read how an API splits its results and caps calls, to estimate how long a full sync will take and to decide how the product should behave when the limit is hit.
Lesson objective
By the end of this lesson, you will be able to read how an API paginates its lists and limits the number of requests, estimate the number of calls and the duration of a synchronization, and specify the integration's behavior when a limit is reached.
Topics covered
- pagination
- rate limits
- rate limiting
- data sync
In the glossary
Where it fits
An integration that lasts
How does the integration withstand large volumes, limits, outages, duplicates and new versions?
Lessons in this module
- Pagination and rate limits (this lesson)
- Webhooks and idempotency, with no duplicates and no lost events
- Sandbox, production, versions and deprecations
What you will learn in this module
This lesson is part of the course Design and test an API integration as a PM
- Specify pagination, rate-limit handling, webhooks and idempotency for an integration that withstands volumes, outages and duplicates.
- Plan environments (sandbox, production), versions, breaking changes and deprecations in the spec and the test plan.
Related courses
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Git for PMs: ship as a team without putting production at risk
3 hr 30 min
- Tech for PMsAll levelsNo prerequisites: accessible to everyone.
Explain how a web product works, from browser to server
2 hr 30 min
- Tech for PMsJuniorSome basics are useful: introductory knowledge of the topic.
Model your product’s data and query it with SQL
3 hr 30 min