20 Versioning an API and handling breaking changes
This chapter covers
- Changing an API and understanding the impact of changes
- Supporting multiple versions of APIs and schemas
- Avoiding breaking changes
We added support for multiple pets and pets other than dogs in chapter 16. In the OpenAPI definition for the PetSitter API, the Job schema had a property changed from dog to pets. José noticed that this had a knock-on effect with Max, the frontend developer. If Nidhi had released the backend change before Max was ready, a large portion of the PetSitter website would have stopped working. But because the team communicates often, this was hardly a problem—they could easily coordinate how to roll those changes out. But what will happen when the ...
Get Designing APIs with Swagger and OpenAPI now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
