SDN APIs & The Next Wave Of Innovation - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Comments
SDN APIs & The Next Wave Of Innovation
Newest First  |  Oldest First  |  Threaded View
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Ninja
6/23/2014 | 1:38:58 PM
Re: Tomato, tomahto
But we've seen lots of examples where companies with dominant marketshare have "embraced and extended" a standard that would make it incompatible, except they control so much of the market that their extensions become de facto standards.


I'm curious if you think today's environment makes it easier to force a proprietary extension on the market, or if there are so many changes and so much upheaval that vendors are more compelled to stay within the boundaries because they need to interoperate?
steveshahcitrix
IW Pick
100%
0%
steveshahcitrix,
User Rank: Strategist
6/18/2014 | 8:53:10 AM
Re: Tomato, tomahto
Hi Lorna - Yes, and no. Let's start with no -- the API spec is the API spec much like Ethernet is Ethernet. Extending the API basically makes you incompatible so unless you can get the market accept your changes (either through market share or future versions of the standard) you're out of luck. The yes side is that once you get a call, you can be creative which could mean additional configuration that is outside of the scope of the standard.


For example, the way that you read/write files from Unix has a standard API set by POSIX eons ago. Follow the API, and your application will work across multiple flavors of Unix without issue. Each flavor of Unix then offered up their own flavor of interpreting the API by creating different filesystems with different performance and resiliancy characteristics. The first vendor to create a filesystem that could handle a hard shutdown without needing to run a repair process on the next boot (IBM with JFS, if I recall correctly) had a differentiation even though they tied into the same POSIX API.

-Steve
Lorna Garey
50%
50%
Lorna Garey,
User Rank: Author
6/17/2014 | 1:38:54 PM
Tomato, tomahto
Is saying that "within that standard there is a lot of room for differentiation" basically stating that APIs are a new way to "embrace and extend" ... in other words, lock in via proprietary hooks?


2020 State of DevOps Report
2020 State of DevOps Report
Download this report today to learn more about the key tools and technologies being utilized, and how organizations deal with the cultural and process changes that DevOps brings. The report also examines the barriers organizations face, as well as the rewards from DevOps including faster application delivery, higher quality products, and quicker recovery from errors in production.
News
How COVID is Changing Technology Futures
Jessica Davis, Senior Editor, Enterprise Apps,  7/23/2020
Slideshows
10 Ways AI Is Transforming Enterprise Software
Cynthia Harvey, Freelance Journalist, InformationWeek,  7/13/2020
Commentary
IT Career Paths You May Not Have Considered
Lisa Morgan, Freelance Writer,  6/30/2020
Register for InformationWeek Newsletters
Video
Current Issue
Special Report: Why Performance Testing is Crucial Today
This special report will help enterprises determine what they should expect from performance testing solutions and how to put them to work most efficiently. Get it today!
White Papers
Slideshows
Twitter Feed
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Sponsored Video
Flash Poll