Posted on 03-14-2013
I see a lot of new API platforms emerge, and often times you see them deploying their own solutions to problems that are actively solved by top API platforms, and are already adopted by common mobile and web app users.
The best example of this is with authentication. Its growing more and more common that you don’t build your own login, you use Facebook, Twitter, LinkedIn, Google or Github oAuth.
It seems to me that when it comes to other common resources, the same could be applied. So I’m exploring what my essential stack of API driven resources might look like:
I could do quite a bit with this assembled as a single backend stack, if it included a regular datastore, key-value store, user management and other essentials for building apps.
It seems to me that new platforms shouldn’t always create new silos, but bridge the existing ones that we depend on already.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- With Number Of APIs Continuing To Grow Account Automation Will Be Key
- History Of APIs: NOAA APIs Have Been RESTful For Over 20 Years
- Understanding More About The Web Communications Platform Respoke
- Swagger Definition Driven Sandbox And Simulation Data Templates For APIs
- Swagger API Definition Mapper
- Moving Beyond Just The PDF With A Single Page Report (SPR)
- Join Me For APIDays Berlin And APIStrat Europe This April 24th-25th 2015
- A Market For API Developer Credits
- Where Do Developers Get Idea That APIs Should Never Go Away?
- The Context.io API And Thinking Out Of The Box When Crafting APIs