Full Life Cycle API Management is not enough, let’s try 8K API Management
By Arnaud Lauret, November 17, 2021
You didn’t knew that API Management was old and you needed a “Full Life Cycle” API management solution to help you achieve your API strategy? Well, I didn’t. To be honest, though the term is quite old, I didn’t realized until recently that “Full Life Cycle API Management” started to replace simple “API Management”, at least in software vendor communications. But what if I tell you that this “Full Life Cycle” version is already dead? What if I tell you that you need 8K API Management?
What is (Full Life Cycle) API Management?
When someone says “API Management”, that often means “exposing APIs on an API Gateway and possibly put them on a developer portal”. It’s very rare that it actually means “the process of creating and publishing web application programming interfaces, enforcing their usage policies, controlling access, nurturing the subscriber community, collecting and analyzing usage statistics, and reporting on performance.” (Wikipedia). That definition is wider, it’s about process, how you create and publish web APIs, and not only tools. It’s more precise, APIs are exposed on a gateway in order to enable access control. And It also includes concerns that goes beyond exposition itself, like taking care of the consumer (subscriber) community.
Full Life Cycle API Management goes a little bit further but not that much, as show in the various definitions below:
|Gartner||Full life cycle application programming interface (API) management is about the planning, design, implementation, testing, publication, operation, consumption, maintenance, versioning and retirement of APIs.|
|Axway||Full lifecycle API management is the entire lifespan of an API that begins at the planning stage and ends when an API is retired. It provides the platform for digital strategy, building ecosystems, and running an effective API program.|
|MuleSoft||Full API lifecycle management is the process of overseeing an API from its creation to retirement across its full life span. This includes everything from designing, publishing, documenting, securing, and analyzing APIs.|
|WSO2||An APIs goes through different stages in its lifespan until it is retired. Full lifecycle API management solutions provide the means to manage these stages as well as the transition from one stage to another.|
With Full Life Cycle API Management, we get a more complete definition of the “process of creating and publishing” APIs, it’s about their “planning, design, implementation, testing, publication, operation, consumption, maintenance, versioning and retirement”. The process is about managing APIs from their conception to their death.
The latest Gartner Magic Quadrant for Full Life Cycle API Management mostly lists vendors providing an “API Management” solution, hence an API Gateway and possibly a develop portal. Such vendors are for instance Axway, Google (Apigee) or Microsoft. But there are 2 vendors that are not API gateway vendors: SmartBear and Postman, they both provide API design, documentation, mocking and testing solutions. That’s the first crack in the Full Life Cycle API Management building we’ve known for years. These 2 providers show that Full Life Cycle API Management is more than just the basic solution of API Management (All in one API Management solution) we have seen these last years. And it’s even more than that. Indeed, Full Life Cycle API Management is dead, long live 8K API Management.
What is 8K API Management?
Why the term 8K? It’s a reference to the TV domain: once there was Full HD, then 4K then 8K. More and more pixels, allowing crisper image with higher definition but also larger ones, showing us more than we could seen before.
Full Life Cycle API Management has been monopolized by all in one API Gateway based tools, narrowing our vision. But none of them is actually able to cover efficiently the full life cycle, the presence of SmartBear and Postman in the Gartner Magic Quadrant is the visible part of the iceberg. Tools such as Stoplight Studio (a GUI to design API) or Microcks (API mocking) are a few among many others that you could take advantage to fully cover the Full Life Cycle API Management.
The “Full life cycle” term is also narrowing our vision to the life and death of APIs, forgetting what is needed around all that. The whole API governance space definitely lacks tools. As I stated in an earlier post, we need tools for API design reviews, and that’s only an example.
And more than tools, don’t forget that “however you call it API management” is not only about tools but also people. How do you make them realize how API can help their company, how do you teach/train/coach people to plan, design, … the right APIs the right way?
This is 8K API Management. API Management with higher definition and wider scope. API Management with more specialized tools, covering more concerns. API Management not only focusing on tools but also people.