Your development team has created a new version of their service's API.
You need to deploy the new versions of the API with the least disruption to third-party developers and end users of third-party installed applications.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
Option A is the correct answer.
Here is a detailed explanation of the steps involved in deploying the new version of the API with the least disruption to third-party developers and end users of third-party installed applications:
Introduce the new version of the API: Deploy the new version of the API on a separate endpoint or URL, different from the old version of the API.
Announce deprecation of the old version of the API: Notify third-party developers and end-users of the old API about the deprecation of the old API version. This notification should include a clear timeline for when the old API will be turned down.
Deprecate the old version of the API: Once enough time has passed, the old version of the API should be officially deprecated. At this point, developers and end-users should be informed that they need to switch to the new version of the API.
Contact remaining users of the old API: Reach out to any remaining users of the old API to remind them of the deprecation and encourage them to switch to the new version of the API.
Provide best effort support to users of the old API: While the old API is still operational, make best effort to support users of the old API with any issues they may have. However, no new features or major bug fixes should be introduced to the old API.
Turn down the old version of the API: Finally, after an adequate amount of time has passed and all users have switched to the new API, the old version of the API should be turned down.
By following these steps, the deployment of the new version of the API can be done with minimal disruption to third-party developers and end-users of third-party installed applications. Option A is the best answer as it follows this approach.