Posted on 03-22-2011
Your server or storage could disappear at any moment, because its virtualized! Sure, as would any server or storage, that's why I have plan A and B, and in the clouds I have C & D as well. I plan for failure no matter where my infrastructure is located.
Your data is not secure in the clouds! Security is a concern everywhere, make sure and have thorough security plan that is revisited regularly.The naysayers are now making their arguments about APIs
Your API access could be shut off at any time! I don't think this is any secret about APIs. This is why there are terms of service that you must read and follow. Your application needs to take this into consideration with ALL the APIs it uses -- whether they're from developer-friendly companies or not, and then operate accordingly.
An API owner could decide to poach business from its community at any time! Again I don't think its a secret. APIs are a form of R&D for companies, this is open territory for everyone to innovate. In perfect world an API owner communicates openly with developers and partners about opportunities in the ecosystem, plans to monetize, and where partner opportunities exist. I'm not saying these dangers aren't real. They are. What I'm saying is that none of this should come as a shock. You build and plan around these potential issues just as you would with any other technologies you invest in. What if Google Apps goes down? What if your supplier goes out of business? What if FedEx doesn't arrive on time?Open APIs aren't really the problem here. If a company is built entirely around a single API ecosystem, maybe the owners should consider diversification into other areas, expanding their business. The fault is with the business strategy; it's not the fault of the API. If an API ecosystem grows large enough where business opportunities develop that are ripe for picking by companies or poaching by the APIs owners, then the responsibility is on the API owner to establish a partner strategy that considers and includes ecosystem developers. It's not the fault of the API. Technology is transforming a lot of industries right now. Open APIs are at the heart of this. This is a good thing. Open APIs drive developer and business innovation, and as this occurs there are going to challenges with monetization, business strategies, licensing, ownership, security, and privacy. Let's not blame the API or scare people off from using APIs by freaking out about the dangers. Let's identify the pitfalls, understand their value and establish healthy ways to integrate with APIs, to build healthy business and vibrant ecosystems around them.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- I Am Using Kimono Labs To Fill In Gap For Companies Who Do Not Have AN RSS Feed For Their Blog
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma