Posted on 06-15-2014
Netflix officially announced they will be ending support for their public API. Its no surprise, as they announced early in 2013 that they would longer accept new registrations for the API.
While I think that Netflix could have put more resources into their API, and fought harder to make their public API a success, I still consider Netflix to be one of API pioneers that we can learn from when crafting our own API strategy.
While the public Netflix API was not a success, the internal and partner API strategy at Netflix was a success. APIs have allowed the company to scale into the cloud, grow internationally, and expand to sever over 1000 devices via their trusted partner network.
In addition to the internal API success at Netflix, they have been amazing at sharing their knowledge and experience with the wider API community via their blog, conferences like API Strategy & Practice, and in books like APIs: A Strategy Guide, available on O'Reilly Publishing, written by Daniel Jacobsen, Greg Brail and Dan Woods.
Another positive byproduct of Netflix API operation, is that the company has been prolific in open sourcing the technology that goes into the API stack. When you visit the Netflix Github account, you will find a wealth of open tooling that they have worked hard on, and opened up for public use.
API success varies widely from company to company, sector to sector, and it doesn't always look like you think it will—this is part of the API experience. Just because Netflix doesn't reflect one vision of API success that open developers believed in, it doesn't mean Netflix as a whole was an API failure. There are plenty of lessons to learn from their public API failure, as well as their internal API success.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- WordPress Style API Modules For Government
- The Heroku HTTP API Design Guide
- What I Have Been Calling API Trends, Are Slowly Being Baked Into API Operations
- FDA Finding Their API Mojo With A New Drug Label API
- Adding PokitDok To Healthcare Research And The API Stack (Well They Did)
- Why I Am Continuing To Integrate Zapier In My Business Workflow
- Who Is Going To Build The Uber API Platform For The Sharing Economy?
- The API Focused Dev Shop
- Route SMS Messages To Google Spreadsheets Via Twilio API With TwilioSheet
- Publishing Your APIs To Product Hunt
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio
- Every API Provider Should Have A Logo And Branding Page
- What Is An API First Strategy? IT architecture And Catalyst For Engagement
- The Speed Of Federal Government When It Runs On Github
- Swagger, APIs.json, And Review For The New Developer.Trade.gov
- Student, Instructor, Classroom, Class, And Course API Planning At BYU
- Can You Add My API To Your Website Listing?
- Adding Google To List Of API Deployment Companies
- What Is An API First Strategy? Adding Some Dimensions To This New Question
- The Five Month Journey Toward A Stable APIs.json Discovery Format