1 What is APIOps?

1.1 What is APIOps?

Many companies 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 an API-design-first approach. But with all this, they still see a big gap between their governance standards and what they implement. This execution gap results in shipping APIs that are not compliant with their usability and security standards are not well-documented, discoverable, and accessible, or have performance, reliability, and scalability issues. Along with all this, they face an expensive and inefficient API-development process with a long lead time to getting their API products to market.

1.1.1 Scaling API delivery: problems arising.

1.1.2 Tackling the scaling problem

1.2 APIs and API Products

1.3 Why should you care about APIOps?

1.4 Key principles of APIOps with OpenAPI

1.4.1 Create and validate your API definition files before build

1.4.2 Store API definitions in version control

1.4.3 Automate API standards compliance

1.4.4 Run API conformance checks

1.4.5 Store declarative API gateway configurations in version control

1.4.6 Continuously reconcile the desired and actual state

1.5 APIOps practices you will learn in this book

1.6 How APIOps affects API governance

1.7 Challenges with adopting APIOps with OpenAPI

1.8 Summary