Plugin Infrastructure For Every Stop Along The API Lifecycle
03 Aug 2017
I’m continuing my integration platform as a service (iPaaS) research, understanding how API providers are quickly integration with other platform, I am also looking into how API service providers are opening up their services to the entire API lifecycle. I’m seeing API service provides offer up a default set of integrations with other platforms, ad in some cases using Zapier by default–opening up 750+ other API driven platforms pretty quickly. Another dimension of this that I’m tracking on is when API service providers offer up plugin infrastructure, allowing other platforms to develop plug and play integrations that any platform user can take advantage of.
I’ve added a separate research area to tune into what types of integrations platforms are introducing via plugin infrastructure. I’m trying to understand how plugins are evolving from being more about platform, browser, and other common forms and becoming more API lifecycle middleware (for lack of better term), like Tyk. I want to be aware of each of their approaches, and how different stops along the API lifecycle are embedding scripting engines, injecting integrated features into operations, and making it part of any continuous integration and deployment workflow(s). Like the other areas of my API lifecycle research, I will stop in from time to time, and understand if plugin API infrastructure is evolving and becoming more of a thing.