QuestionQ73

VerifiedApplying site reliability engineering practices

Your development team has released a new version of your service's API. You need to roll out this new API version while causing the least possible disruption to third-party developers and end users of third-party applications that use the API. What should you do?

Explanation

Minimizing disruption requires following an orderly API lifecycle: first make the new version available, then formally announce that the old version will be deprecated (giving users advance notice), then mark it as deprecated, then proactively contact any developers still using the old version, then continue offering best-effort support to those stragglers, and only after all that turn down (retire) the old version. This sequence avoids cutting off developers before they have a replacement, before they've been warned, or before they've had a chance to migrate with support.

Community Discussion

No comments yet. Be the first to start the discussion!