3 years ago

Category: Business, Database

As with any product lifecycle, a key responsibility for API architects and API product owners is deciding when to sunset or retire a feature or offering. The API lifecycle is no different, but requires careful planning to carry out the deprecation to minimize customer impact.

Thus, a normal course of business is to sunset an API or service that is no longer aligned with today’s requirements and objects.

Improve the developer experience and reduce bloat Sometimes you want to refactor your API spec to “make it cleaner” and easier to understand from a customer perspective.

API is inefficient or bug-prone Some APIs may be bug-prone or subject your infrastructure to reliability issues.