1 What is APIOps?

Many organizations aim to build high-quality, well-documented, easy-to-use APIs, but they struggle with being able to implement this in practice. They may have API governance standards and functions and even adopt a design-first approach to API development. However, even with all of this, they still see a big gap between their governance standards and what they implement. This execution gap often leads to shipping out APIs that fail to meet their usability and security standards, lack proper documentation, and are neither discoverable nor accessible. Additionally, these APIs may suffer from problems related to performance, reliability, and scalability. The organization may also suffer from an expensive and inefficient API development process with a long lead time to getting their API products to market.

1.1 Scaling API delivery: Problems arising

1.2 Tackling the scaling problem

1.3 APIs and API products

1.4 Why should you care about APIOps?

1.5 Key principles of APIOps with OpenAPI

1.5.1 Use a design-first approach to API development

1.5.2 Store API definitions in version control

1.5.3 Automate API standards compliance

1.5.4 Run API conformance checks

1.5.5 Store declarative API gateway configurations in version control

1.5.6 Continuously reconcile the desired and actual state

1.6 APIOps practices you’ll learn in this book

1.7 How APIOps affects API governance

1.8 Challenges with adopting APIOps with OpenAPI

Summary