APIs are everywhere. With OpenAPI 3 and REST becoming the well-accepted standard among developers, a significant portion of an enterprise developer’s job consists of creating, publishing, discovering, and consuming APIs.
In an environment with a significant number of developers on disparate teams, this inevitably leads to waste: a significant waste of time, effort, and money.
Developers waste energy reverse-engineering inadequately documented APIs. They waste time identifying the right API. They burn unnecessary cycles figuring out how to make their API widely available.
Once they have an API deployed, there’s a waste of time and energy making sure the API is adequately secured and that it’s shared across a large organization, not to mention making sure those APIs are maintained and kept up to date.
Architects may spend undue time building out a central clearing house for discovering APIs and a central gateway for deploying them.