Serverless

Adjective · Noun · Development · Origin: 2014

Definitions

  1. Serverless is a cloud computing model where the provider dynamically manages server allocation, scaling, and infrastructure, so developers deploy only their application code. Servers still exist, but the developer never provisions, patches, or scales them directly. The most common form is Functions as a Service (FaaS), where individual functions execute in response to events like HTTP requests, file uploads, or queue messages. AWS Lambda, Google Cloud Functions, and Azure Functions are leading platforms. Billing is typically pay-per-invocation, meaning idle time costs nothing. Tradeoffs include cold start latency (delay when a function spins up after inactivity), execution time limits, vendor lock-in, and more complex debugging compared to traditional deployments.

    In plain English: A way to run code in the cloud without worrying about servers — you just upload your code and it runs when needed, and you pay only for the time it actually executes.

    Example: "Serverless isn't serverless. Cloud isn't a cloud. Artificial intelligence isn't intelligent. Welcome to tech nomenclature."

Etymology

2012
Iron.io uses the term 'serverless' in a blog post, describing a future where developers never think about servers
2014
AWS launches Lambda, the first major serverless compute platform, making the concept concrete and commercial
2018
'Serverless' becomes the most over-hyped and over-debated term in cloud computing — servers still exist, of course

Origin Story

The most misleading name in cloud computing (there are definitely servers)

**Serverless computing** is the tech industry's most successful misnomer. There are absolutely servers involved — you just don't manage them. The term gained traction around 2014 when AWS launched **Lambda**, a service that ran your code in response to events without requiring you to provision or manage any infrastructure.

The concept existed earlier: Platform-as-a-Service (PaaS) offerings like Heroku and Google App Engine abstracted servers away in the late 2000s. But "serverless" as a marketing term crystallized with Lambda and was quickly adopted by Google Cloud Functions and Azure Functions. The name stuck because it captured the developer experience: you write a function, upload it, and it runs. No servers to patch, scale, or babysit.

The backlash was immediate and ongoing. "Serverless is like 'wireless' — there are still wires, just not *your* wires" became a common joke. But the abstraction is genuinely powerful: for many workloads, serverless reduced operational burden by orders of magnitude, even if the name drives pedants slightly crazy.

Coined by: AWS / cloud computing community

Context: AWS Lambda launch, 2014

Fun fact: The domain serverlessconf.io was registered in 2016 for a conference entirely about serverless computing. The conference was, of course, hosted on servers.

Related Terms