Posted on 04-26-2014
I’ve been studying the API space exclusively for the last four years, and have worked hard to try and understand the space by studying the history of APIs, and as a result I can confidently say we are smack dab in the middle of what I consider to be an enterprise phase.
In 2013 and 2014 I’ve seen the enterprise across multiple business sectors turn their attention to this curiosity called the web API. So why is the enterprise so interested in APIs? Many technologists from the enterprise claim that it is no difference than their own earlier SOA efforts, but there has to be more under the hood, that is attracting the enterprise, beyond just a shiny new label, API—so what are they?
- Simplicity - Keep things small, modular and intuitive
- Access - You should be widening access to your resources, not ever limiting
- Openness - While not everything should be 100% open, be as open as possible
- Transparency - Provide insight into operations and your roadmap allowing consumers to operate in alignment
- Communication - Two way communication between you and your consumers
- Privacy - Protect the privacy of your consumers
- Ownership - Be open to alternative licensing and ownership of content and data that is favorable to consumers
- Legal - Be as open as you can be with copyright, patents and trademark in API initiatives
- Revenue - Acknowledge the monetization needs of your consumers
- Quantify - Define and understand how digital resources are being consumed
If you're looking at the web API phenomenon purely through a technical lens, as many SOA practitioners do, you will not even see most of these characteristics—they are irrelevant to your tech driven goals. In my opinion this humanization of a company’s digital resources, which historically have been locked up, defined and controlled by IT gatekeepers, is the single most important lesson for the enterprise when it comes to web APIs.
In 2014, as you are planning your API strategy, don't make the mistake in seeing APIs as purely a tool in the SOA toolbox, as they were over 10 years ago. Long ago web APIs jumped out of the enterprise petri dish, experienced the oxygen available within the public sphere and developed some life giving characteristics that will be critical to the enterprise surviving and thriving in the coming years.
I will be talking at IBM Impact in Las Vegas next week on this topic.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- New Indix API KickStart Program Reduces Costs For Developers
- Getting To Know Mike Kelly For The API Craft 2014 Detroit Hypermedia Panel
- A Shared, Distributed Experience(Metrics) Layer For The API Driven Application Stack
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs