Fork me on GitHub

I wrote about the interesting approach by Plivo the other day around their Voice Chat API, in which one thing they did really caught my eye, and reflects what I think is the future of APIs—the deployment of the API to Heroku.

This type of very modular, cloud deployment of fine grain APIs is something that I’ve blogged about recently in Modular APIs Driven From Github Blueprints Using OpenShift, Server Side API Templates On AWS Cloud Formation And OpenShift, and Caching APIs With CloudFormations Or OpenShift.

As part of the Voice Chat API, Plivo allows you to deploy an instance of the open source audio conference API to your own Heroku account. This is an interesting way to empower developers to deploy API resources, allowing them to allocate them within their preferred cloud environment, whether it is Heroku, Amazon, OpenShift from Redhat, or any other provider.

I haven’t investigated if there are any dependencies between the Voice Chat API and Plivo, but even with dependencies, this approach still holds a lot of promise. This gets us closer to some of my earlier thoughts around virtual API stacks, that allow us to build, manage and put to use the most meaningful stack of APIs possible for our applications—think backend as a service (BaaS), but custom fit to exactly the resources we need.




comments powered by Disqus