Why isn’t Serverless obvious to everyone?

Paul Johnston
Oct 5, 2017 · 1 min read

When we used to build websites in the beginning, we had to do everything didn’t we?

Things like session management, database connections and routing.

Anyone remember actually having to use cgi-bin? *raises hand*

But now, it’s pretty obvious that we don’t need all that, and we use frameworks.

We’ve stopped “building our own” and have actually said that these frameworks provide value.

So why don’t we do that for Serverless?

Serverless is simply using tools that do what we would otherwise be doing by running servers, or instances or containers.

So why are people so averse to Serverless?

Why aren’t people saying “I don’t want to build my own server, so I’ll go Serverless”?

It almost feels hypocritical not to go with Serverless.

Or are there people out there who still don’t use frameworks, and libraries to build web applications any more, because they prefer to “roll their own”?

Or am I wrong?

Paul Johnston

Written by

ServerlessDays CoFounder (Jeff), ex AWS Serverless Snr DA, experienced CTO/Interim, Startups, Entrepreneur, Techie, Geek and Christian