The State of API Management
“Integration is the new lock-in feature.”
(Anthony Doerga, CSO, AppyThings)
Infrastructure nowadays is delivered as code and in a way that allows it to be run at different cloud providers or even in on-premise data centers. Consequently, infrastructure software vendors and cloud platforms are implementing new lock-in tactics to retain customers and prevent churn.
The obvious way to do so is to make sure these universal workloads are published through your gateways and to make these endpoints hard to move. Controlling the integration of different workloads and controlling the publishing of your APIs thus is crucial for these types of companies. This is the reason Google bought Apigee, Salesforce bought Mulesoft and Microsoft bought Apiphany.
Customers need to take back control over their destinies. The past has shown that companies that preserve their ability to be agile and embrace changes in technology have a vast edge over their competition. Moreover, acting vendor-agnostic increases the competition in the market which in turn eventually leads to better products and decreased costs.
The way forward: API Management 3.0
The way to achieve this is simple: Instead of using API Management solutions, which are bundled and tailored towards one single API platform (or runtime), one needs to decouple the Management, the provisioning, and the governance from the runtimes. API Management needs to become its discipline with its own vendor-agnostic, standards-based products. APIIDA wants to lead this disruptive change in the industry and create the best tools in the marketplace to get the job done.
Solutions and products developed by APIIDA liberate APIs from the underlying runtimes, enable rapid change and improve governance and compliance at the same time. No matter if the task is to migrate from one API platform to another or if customers run multiple platforms at the same time in a “the right tool for the job” approach, APIIDA has them covered.
This separation of API Management and API runtimes and the strong focus on APIs as an entity of their own rather than just a proxy running on a gateway is what we describe as the third iteration of API Management, APIM 3.0.