Source: thenewstack.io
Three Horizons of Your API Journey
For nearly 20 years, every business that uses software has been on a journey to API adoption. Mirroring the cloud native application trend and empowered by “shifting left,” developers, site reliability engineers (SREs), DevOps and platform engineering teams have pushed back against this top-down approach to an API solution.
Continuing the journey to a full API stack, the second horizon of API adoption is characterized by the creation of an organization-wide API strategy.
At this third horizon stage, teams establish comprehensive approaches and governance for all types of APIs, including internal, partner, third-party and (if applicable) public APIs.
Because the API stack is flexible and loosely coupled, this horizon stage is where the platform ops team should evaluate new technologies that could help their organization improve their API systems — new formats like GraphQL, generative AI tools for automated and updated documentation and languages like Denon that generate API-friendly code out of the box.
Continuing the journey to a full API stack, the second horizon of API adoption is characterized by the creation of an organization-wide API strategy.
At this third horizon stage, teams establish comprehensive approaches and governance for all types of APIs, including internal, partner, third-party and (if applicable) public APIs.
Because the API stack is flexible and loosely coupled, this horizon stage is where the platform ops team should evaluate new technologies that could help their organization improve their API systems — new formats like GraphQL, generative AI tools for automated and updated documentation and languages like Denon that generate API-friendly code out of the box.
Related Articles
Community Partners
DevOps Careers