Serverless

Ulf Schneider, November 2023

A server must always be on.

Image: https://de.wikipedia.org/wiki/CERN_httpd

The sticker saying This machine is a server. DO NOT POWER IT DOWN!! is a way of protecting the server

In Serverless are many servers, but they belong to someone else

The term Serverless describes the developer experience

With Serverless

Developers will not recognize servers, nor manage and interact with them ¹

ibm.com/topics/serverless ↩︎

Serverless can be seen as a current last step of the virtualization evolution

The virtualization evolution ¹

Hardware servers

↓

Virtual machines

↓

Containers

↓

Serverless

ibm.com/blogs/nordic-msp/serverless/ ↩︎

Let's examine the traits of each evolutionary step

Hardware servers

have to be located somewhere (think of cabling, cooling, power-supply, and physical protection)

Hardware servers

have to be installed with software from the ground up

Hardware servers

have to be replaced by new hardware when they become too old

Hardware servers

have to be administered

Virtual machines

decouple from the underlying hardware and operating system

Virtual machines

can be prepared once and installed multiple times on different hardware servers

Virtual machines

can be applied multiple times to a single hardware server

Virtual machines

have to be administered

Containers

can do what virtual machines can do

Containers

are more lightweight (cpu, memory, storage) than virtual machines

Containers

can be distributed more easily than virtual machines

Containers

startup much faster than virtual machines

Containers

have to be administered

Serverless

abstracts away any notion of servers and infrastructure

Serverless

does not require any kind of administration (or minimal)

Serverless

relies on a cloud provider offering the service (IBM, Google, Microsoft, Amazon)

Serverless

is payed per usage

Serverless

scales up and down automatically

Serverless

is reliable and fast around the globe

Serverless

puts the business logic into focus

Serverless covers

functions

storage

authentication

monitoring

alerting

In Serverless are many servers, but they belong to someone else

Image: Edgar Landivar, https://x.com/elandivar/status/868321220453969920

Serverless

A server must always be on.

In Serverless are many servers, but they belong to someone else

The term Serverless describes the developer experience

Developers will not recognize servers, nor manage and interact with them 1

Serverless can be seen as a current last step of the virtualization evolution

The virtualization evolution 1

Hardware servers

↓

Virtual machines

↓

Containers

↓

Serverless

Let's examine the traits of each evolutionary step

Hardware servers

have to be located somewhere (think of cabling, cooling, power-supply, and physical protection)

have to be installed with software from the ground up

have to be replaced by new hardware when they become too old

have to be administered

Virtual machines

decouple from the underlying hardware and operating system

can be prepared once and installed multiple times on different hardware servers

can be applied multiple times to a single hardware server

have to be administered

Containers

can do what virtual machines can do

are more lightweight (cpu, memory, storage) than virtual machines

can be distributed more easily than virtual machines

startup much faster than virtual machines

have to be administered

Serverless

abstracts away any notion of servers and infrastructure

does not require any kind of administration (or minimal)

relies on a cloud provider offering the service (IBM, Google, Microsoft, Amazon)

is payed per usage

scales up and down automatically

is reliable and fast around the globe

puts the business logic into focus

Serverless covers

functions

storage

authentication

monitoring

alerting

In Serverless are many servers, but they belong to someone else

Thank you

Developers will not recognize servers, nor manage and interact with them ¹

The virtualization evolution ¹