Posted on 11-12-2013
I've been working through several demos of how to go from common data sources like MySQL and Google Spreadsheet to API over the last couple of weeks. So far I have five basic working demos:
- MySQL to API
- Local JSON to API
- Github JSON to API
- Public Google Spreadsheet to API
- Private Google Spreadsheet to API
These demos are meant to show how easy it is to deploy a simple API from common places you already have data stored. Right now I'm building them in PHP, but will also be building Python, Ruby and Node.JS versions.
These exercises are meant for my newbie readers but are also helping me see API deployment in different ways. I realize how difficult it is to write code that will work for all scenarios. There is a lot of custom work on the data store side, as well as possible the API side, making me feel like it is best to use an API definition in the middle.
With this in mind, the next phase of my API deployment tools will be about generating API definitions, which currently will be Swagger, but will also develop RAML and API Blueprint versions of the same code eventually.
Once I have some data store to Swagger tooling I will evolve some of the code I have for generating APIs from Swagger definitions.
Then I will have the different custom parts decoupled from each other, all centered around an API definition and data model which I can publish in API Commons and evolve in an open, collaborative environment where everyone can benefit, and contribute to my API work.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Which Building Blocks Should I Use As Part Of My API Support Strategy
- Common Building Blocks of Cloud APIs
- Viewbook Uses Flickr API Design When Designing Their Own
- Expanding An API Designers Horizon Using Apiary
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use