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

Introducing Vendorless APIs and Microservices

DZone's Guide to

Introducing Vendorless APIs and Microservices

Okay, first the hardware turned into the cloud, then our servers joined them there. Now we don't even need servers? What can this mean?

· Integration Zone ·
Free Resource

SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.

I'm a big fan of the concept of serverless APIs and microservices, but not so much of the name. I get it, the space needs new concepts to rally around, and I'm the first to admit even the concept of an API is nonsense, but when people say serverless, it always makes me chuckle — especially when people work so hard to sell it (who am I to make fun of that?).

Image title


Often when I come across a serverless solution, it is often bundled with the phrase "100% serverless," a description which usually then contains the two-six vendor solutions used to deploy said serverless solution. I know there is no use in pointing out there are always servers behind serverless solutions, but can I at least point out the vendor dependencies involved? Are the vendor dependencies better or worse than our dependencies on servers (that never went away)? IDK. WTF. BBQ.

In support of this line of thinking, I want to start promoting the concept of vendorless APIs and microservices. You know the ones that employ web and open source technology? Then I can label my microservices as vendorless, made from the finest gluten free, organic HTTP, free-range web concepts available today!

Download A Buyer's Guide to Application and Data Integration, your one-stop-shop for research, checklists, and explanations for an application and data integration solution.

Topics:
microservices ,api ,web development

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}