Summary

At this point, you know how you can use API versioning to release changes efficiently. You know what the different API versioning strategies are and how consumers can use them to request the version they want to use. You also know that the easiest way to promote an automatic migration to your latest version is to make it the default one. Whenever consumers don’t specify which version they want to request, you serve them the latest available one. You know what deprecating an API version means and how you can control its impact by defining a sunset policy. You also know that the highest impact comes from changes that create incompatibilities with the previous version-breaking changes. You know how to identify breaking changes by generating a diff between two API versions. Additionally, you know what types of differences can be considered breaking changes. Finally, you know the options you have for communicating changes to your whole user base. You know that having an up...