How to explain serverless in plain English

How to explain serverless in plain English

Serverless confuses people: We are talking about less management of servers, not fewer servers. Here's how to explain this trend – and what it means to development – to anyone

417 readers like this
CIO Engaging, retaining and co-creating IT

The baking explanation of serverless

You only pay for the cakes that were ordered and are free to invest your time and resources elsewhere.

“A good analogy is selling cakes,” says Rami Sass, CEO at WhiteSource. “You can buy the ingredients, bake it, and sell it yourself, or you can give your recipe to a contractor and have them bake the cake every time someone orders one from you and get the same result. This is a more scalable process and although outsourcing is usually slightly more expensive than doing it yourself, you only pay for the cakes that were ordered and are free to invest your time and resources elsewhere.”

The BYOB explanation of serverless

Kenna Security’s Gamblin has another hunger-inducing comparison: Imagine you’ve been invited to a backyard barbecue bonanza, and the invitation said “BYOB,” or “bring your own beverage.” That means, Gamblin notes, that the host is promising to take care of everything else – the food, the plates and utensils, the music, the clean-up, you name it. You need to bring only one thing for the party to be a success.

“Serverless can be seen as BYOC: bring your own code,” Gamblin says. “The service provider is going to take care of everything else – networking, servers, OS, etc. – and you just need to show up with the code you want to run.”

The Uber explanation of serverless

Doug McMaster, EVP, managed cloud, at 2nd Watch, says it can be helpful to think of serverless as to IT infrastructure as ride-hailing apps like Lyft or Uber are to car transportation.

“If you own your own car, you have to maintain it: fill it with gas, change the oil, replace brakes,” McMaster says. “Services like Uber and Lyft eliminate these needs, saving you time, money, and effort on the maintenance of your vehicle, while allowing you to focus on what is important – getting from point A to B. Serverless works the same way, freeing up the maintenance time and effort, allowing you to focus on delivering a better customer experience.”

[ Read also: Why Kubernetes is the new application server. ]

Where does serverless fit?

How are organizations using serverless in relation to related trends? Consider this context from Red Hat’s Haff:

"While there are overlaps between the technologies used by FaaS, microservices, and even coarser-grained architectural patterns, you can think of FaaS as both simplifying and limiting. FaaS requires you to be more prescriptive about how you write applications," Haff notes

“Although serverless was originally most associated with public cloud providers, that comes with a caveat. Serverless, as implemented on public clouds, has a high degree of lock-in to a specific cloud vendor. This is true to some degree even with FaaS, but serverless explicitly encourages bringing in a variety of cloud provider services that are incompatible to varying degrees with other providers and on-premises solutions.”

“As a result, there’s considerable interest in and work going into open source implementations of FaaS and serverless, such as Knative and OpenWhisk, so that users can write applications that are portable across different platforms.”

[ Kubernetes terminology, demystified: Get our Kubernetes glossary cheat sheet for IT and business leaders. ]


Then, if "serverless" doesn't

Then, if "serverless" doesn't really describe the whole thing, why use it?...and then have to explain it to folks?...why not call it what it REALLY is?.."Cloud Services" which is something even the most tech-ignorant person can understand...since most people already use a cloud service...(Microsoft's OneCloud...Google's services...heck...even FaceBook has a cloud presence when it comes to people's accounts and profiles!) Sheesh...why make things more complicated than they need to be? Never understood that about the Technology field (which I've been working in since '99!) seems they always want to "label" something or give something a name that doesn't really pertain to what its describing...I mean...c'mon "headless" servers?....WHAT'S THAT!?...Hahahaha!!!!LoL! (and I'm being sarcastic people!...)

Great article though!!


IT leadership in the next normal report

7 New CIO Rules of Road

CIOs: We welcome you to join the conversation

Related Topics

Submitted By Kevin Casey
January 26, 2021

Preparing for an RPA job interview, as a candidate or hiring manager? Check out these RPA-related questions and guidance on developing strong answers. 

Submitted By Sanjay Malhotra
January 26, 2021

The most successful digital transformations are driven by customers, not technology. These 3 strategies help you identify what your customers really want 

Submitted By Stephanie Overby
January 25, 2021

Digital transformation leadership strategies do not match up with traditional IT leadership principles. Make sure you're using approaches that set teams up for success


Email Capture

Keep up with the latest thoughts, strategies, and insights from CIOs & IT leaders.