Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Embrace, Extend, and Exterminate in the World of APIs

DZone's Guide to

Embrace, Extend, and Exterminate in the World of APIs

One of the reasons I like APIs is that they often give a more honest look at what a company does or doesn't do, potentially cutting through the bad part of marketing.

· Integration Zone
Free Resource

Modernize your application architectures with microservices and APIs with best practices from this free virtual summit series. Brought to you in partnership with CA Technologies.

I am regularly reminded in my world as the API Evangelist that things are rarely ever what they seem on the surface. Meaning that what a company actually does, and what a company says it does are rarely in sync. This is one of the reasons I like APIs: they often give a more honest look at what a company does (or does not do), potentially cutting through the bullsh*t of marketing.

It would be nice if companies were straight up about their intentions, and relied upon building better products, offering more valuable services, but many companies prefer being aggressive, misleading their customers, and in some cases an entire industry. I'm reminded of this fact once again while reading a post on software backward compatibility, undocumented APIs, and importance of history, which provided a stark example of it in action from the past:

Embrace, extend, and extinguish, also known as embrace, extend, and exterminate, is a phrase that the U.S. Department of Justice found that was used internally by Microsoft to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences to disadvantage its competitors.

This behavior is one of the contributing factors to why the most recent generation(s) of developers are so adverse to standards and is behavior that exists within current open API and open source efforts. From experience, I would emphasize that the more a company feels the need to say they are open source, or open API, the more likely they are indulging in this type of behavior. It is like, some sort of subconscious response, like the dishonest person needing to state that they are being honest, or that you need to believe them - we are open, trust us.

I am not writing this post as some attempt to remind us that Microsoft is bad - this isn't at all about Microsoft. It is simply to remind us that this behavior has existed in the past, and it exists right now. Not all companies involved in helping define the API space are not interested in things being open, and that there are common specifications in place for us all to use. Some companies are more interested in showing what happens within the community and ensuring that when possible, all roads lead to their proprietary solution. This is just my regular reminder to always be aware.

The Integration Zone is proudly sponsored by CA Technologies. Learn from expert microservices and API presentations at the Modernizing Application Architectures Virtual Summit Series.

Topics:
apis ,integration ,marketing ,microsoft

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}