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?
Join the DZone community and get the full member experience.Join For Free
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?).
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!
Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.