Continuous API Management, 2nd Edition (Continuous development of API) (Category Architecture)

The second edition of this book is about 3 years old, and I have been reading it for the last few months and only recently finished it. I really liked the book and decided to share it with the readers. In this book 12 Chapters that cover many governance-related issues that generalize beyond API management issues

1. The Challenge and Promise of API Management Why companies want to manage their APIs, what problems arise and what opportunities it provides. Here, the authors talk about the main issues discussed in the book. Separately, I note the importance of separation for APIs. (contract)implementation (code) deployment (infrastructure) 2. API Governance A chapter with fundamental concepts for API management and what it means for decision making 3. The API as a Product The Importance of Perceiving APIs as Products (API as a Product). At the same time, the API can be viewed from the point of view of the target audience and make decisions that are best for them. 4. The Pillars of an API Product The main columns on which the API is based. The authors identify the following areas that are considered in detail: strategy, design, documentation, development, testing, deployment, security, monitoring, discovery, change management. 5. Continuous API Improvement How to Live with Continuous Change and How to Manage It 6. API Styles Here the authors talk about the main styles they have. 5. Here they are: tunnel style (RPC), resource style (REST), hypermedia style (RESTful), query style (graphql), event-based style 7. The API Product Lifecycle The life cycle of one API, which consists of stages: create => publish => realize => maintain => The authors analyze in detail how at each stage you need to work out specific pillars. 8. API Teams What roles are needed in teams to effectively develop the API as a product. And not just in a vacuum, but depending on the maturity of the API. 9. API Landscapes Here, authors move from single APIs to their set, which can be perceived as a landscape. The Management at Scale API is based on principles, protocols and practices. This overlaps very much with Google's "API Governance at Scale" paper. told earlier. Plus, the authors introduce the 8v model, which allows you to control the landscape, focusing on different angles. Here are the eight Vs: variety, vocabulary, volume, velocity, vulnerability, visibility, versioning, volatility 10. API Landscape Journey Learn how to implement the Governance API. The authors offer an enabling team model that will help implement and roll out the Governance API processes throughout the organization. 11. Managing the API Lifecycle in an Evolving Landscape Here, the authors cross pillars and 8vs and talk about how they are related. 12. Continuing the Journey The last chapter summarizes the book and prepares readers for the start of Continuous API Management within the company.

P.S. Book covers are presented in next post.

#Architecture #Software #Governance #Management #Leadership #Processes #Leadership