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
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API