Going Serverless:

Code Without Infrastructure

  1. What is Serverless?
  2. Why Serverless?
  3. The Serverless ecosystem
  4. Serverless challenges

@pheasley

1

What is Serverless?

[Code that] is run in stateless compute containers that are event-triggered, ephemeral (may only last for one invocation), and fully managed by a 3rd party. - ThoughtWorks

Stateless compute containers

Event triggered

Ephemeral

Fully managed
by a 3rd party

Not restricted to a single function

Serverless architecture is such a silly name. Of course there are servers, just not ones you need to watch and micromanage all the time - @VilleImmonen

Demo

2

Why Serverless?

Pay per invocation

3 million requests

Runs for 1 sec

Allocated 512MB memory

= $18.34 per month

Managed scaling

Isolated deployments

Time to market

A short history of Cloud computing

Bare metal servers

Virtualisation

Pet servers
vs.
Cattle servers

Hosted virtualisation

Infrastructure as a Service (IaaS)

Hosted environments

Platform as a Service (PaaS)

Serverless functions

Functions as a Service (FaaS)

Serverless Microservices

For the win!
3

The Serverless ecosystem

Serverless Providers

AWS Lambda

Google Cloud Functions

AWS Lambda Event Triggers

Serverless Framework

Demo

4

Serverless challenges

Maturity

Execution duration

Startup time

Authentication

Dev / integration testing

Statelessness

Recap

Thanks.