Posted on 11-16-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.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions