Module 5 of 6Lesson 3 of 3~13 min
Sandbox, production, versions and deprecations
An integration does not end at launch: the API changes and some versions go away. This lesson helps you plan, right in the spec, the move from the test environment to production, the choice of version and how to keep an eye on changes announced by the vendor.
Lesson objective
By the end of this lesson, you will be able to plan in a spec the move from sandbox to production, the choice and pinning of an API version, the distinction between breaking and compatible changes, and the monitoring of deprecations.
Topics covered
- sandbox
- API versioning
- deprecation
- breaking changes
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
- Webhooks and idempotency, with no duplicates and no lost events
- Sandbox, production, versions and deprecations (this lesson)
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