Modular APIs Driven From Github Blueprints Using OpenShift
16 Nov 2013
I'm working on a variety of ways that anyone can easily deploy API on common cloud platforms. I'm working through a series of open and secure, modular API demos written in PHP, using the Slim framework.
All of these demos are pretty basic, but currently I'm deploying them on Amazon EC2, because it is where most of my infrastructure runs and a top platform with wide user base. Ultimately my goal is to make them as simple to deploy as I possibly can, and while EC2 is definitely the leader, I know there are even simpler ways to launch simple APIs in the clouds.
I was doing a survey of which PaaS platforms government agencies allow their workers to deploy projects on, via the US government API group and was reminded of OpenShift, from Redhat. If you aren't familiar with OpenShift, it is a PaaS platform that allows you to define applications in a variety of languages, then deploy, automate, manage and scale in a very modular way.
With OpenShift I can define a very modular application, such as an API running PHP, using Slim framework and even apply what is known as a database cartridge, providing MySQL or Postgres storage for the API--all with a single command line. I can instruct each application to derive its code from a Git location, allowing me to manage a central library of applications, then deploy specific instances as needed.
What I really like about this approach, in addition to the modular design is that I can maintain blueprints for common APIs on Github and reference these designs when deploying APIs via OpenShift. This matches up well with what I'm doing with api.ongithub.com and data.ongithub.com where I working to define simple Git driven approaches to open data and APIs.
Good stuff, I look forward to playing around more.