Are We Ready for Serverless

Are We Ready for Serverless

Subbu Allamaraju

Container World | Feb 27, 2018 | Santa Clara, CA

@sallamar

https://www.subbu.org

More than 50% of

compute may be

stateless

Copyright 2018 Expedia Inc. 2

Observation

Hypothesis


Most of stateless is a

candidate for some

kind of serverless


Hypothesis

Most of state is

moving to managed

cloud services

Capacity demand

Desired capacity

Actual allocated capacity + additional DR capacity?

A dream from 2011


Reality in 2018


A few billion lambda invocations per month

What about state?

S3, Glacier, Aurora,

Elasticache, RDS,

Redshift, DynamoDB,

Neptune, Athena,

ElasticSearch Service,

Quicksight, EMR,

Kinesis, Data Pipeline,

CloudSearch, Redshift,

SQS, SNS, MQ, …

BigQuery, Cloud

Dataflow, Cloud

Dataproc, Cloud

Datalab, Cloud

Dataprep, Cloud

Pub/Sub, Data Studio,

Cloud SQL, Cloud

Bigtable, Cloud

Spanner, Cloud

Datastore, …

Queue Storage, Blob

Storage, Notification

Hubs, Search, SQL

Database, SQL Data

Warehouse, SQL Server

Stretch Database,

Cosmos DB, Redis

Cache, Table Storage,

HDInsight, SQL Data

Warehouse, Event Hubs,

…


Container ecosystem may

or may not play a role


Hypothesis

Are we really ready?


Not suitable for long-running

appsExpensive

Lock-in

Slow on cold start

No local storage

More complex call patterns

Unknown security risks

No standards

Observability is hard?


Habits and inertia

Stateless isn’t always

stateless

Ephemeral isn’t

always ephemeral

Often pet like

?


Fear of the ecosystem

Lock-in worries

Undifferentiated heavy

lifting vs Value

generation?

?


Maturity

Feature gaps

Pricing

Tomorrow != Today

Tooling?


Embrace the paradigm

Learn

Get ready


Technology

Are We Ready for Serverless