Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building an API Product

You're reading from   Building an API Product Design, implement, release, and maintain API products that meet user needs

Arrow left icon
Product type Paperback
Published in Jan 2024
Last Updated in Jan 2024
Publisher Packt
ISBN-13 9781837630448
Length 278 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Bruno Pedro Bruno Pedro
Author Profile Icon Bruno Pedro
Bruno Pedro
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Part 1:The API Product
2. Chapter 1: What Are APIs? FREE CHAPTER 3. Chapter 2: API User Experience 4. Chapter 3: API-as-a-Product 5. Chapter 4: API Life Cycle 6. Part 2:Designing an API Product
7. Chapter 5: Elements of API Product Design 8. Chapter 6: Identifying an API Strategy 9. Chapter 7: Defining and Validating an API Design 10. Chapter 8: Specifying an API 11. Part 3:Implementing an API Product
12. Chapter 9: Development Techniques 13. Chapter 10: API Security 14. Chapter 11: API Testing 15. Chapter 12: API Quality Assurance 16. Part 4:Releasing an API Product
17. Chapter 13: Deploying the API 18. Chapter 14: Observing API Behavior 19. Chapter 15: Distribution Channels 20. Part 5:Maintaining an API Product
21. Chapter 16: User Support 22. Chapter 17: API Versioning 23. Chapter 18: Planning for API Retirement 24. Index 25. Other Books You May Enjoy

Planning for API Retirement

API retirement refers to the intentional and planned discontinuation or deprecation of a whole API, not just a single version. It involves removing an existing API from service, indicating that it is no longer supported and that existing users should transition to an alternative solution. The suggested alternative solution can be an API from another company or a newer one that’s been built to replace the one that’s being retired. Whatever the case, you should create a grace period to allow users to successfully migrate out of the retired API. Keep reading to learn how to manage the retirement of your API effectively.

You’ll start this chapter by understanding when is the right moment to retire an API. You’ll see the key events that can trigger the decision to put an API to rest. You’ll see that the decision to start a retirement process comes from factoring in the costs of keeping your API running against the benefits...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image