The pain of writing serverless functions, paying for resources that are not In use, and runtime unavailability can be a developer’s nightmare. With Serverless containers, You can run any programming language of your choice, pay for resources used, and focus on the business logic of your app.
Serverless Containers are the game changers we have been waiting for. So come and join me in this talk as I demystify Serverless Containers.
Hey! I’m Obinna Odirionye.
- Kubernetes Engineer, Kubermatic.
- Member and Maintainer, CNCF Helm ChartMuseum.
What is Serverless
“Serverless doesn't mean there’s no servers, it means we think
about Servers less”
Scott Hanselman tweet:
What Serverless Offers
● Pay for what you use - Compute
● No server management is required
● Inherently Scalable
● Quick and Fast deployments
Cons of Serverless
● Not built for long running processes - It’s gets better
● Performance issue
● Vendor lock-in is a Risk
● Hard to debug
Ugh! Bad side
Serverless started as
Make a twitter Bot, Build a RESTful API endpoints, Make an S3 ﬁle
replicator and many more…
● Limited Runtime Availability
● Heavily decoupled
● Vendor Lock-in
The bad parts
So Much Problems.
“The Birth of Serverless Containers”
“Serverless has evolved beyond FAAS and functions are an
Kelsey Hightower tweet:
In August 15, 2018, Google Cloud
released Cloud Run - Alpha Release.
The goal was to bring the best parts of
Serverless and Containers together.
The cons of serverless functions were
solved in Serverless Containers.
● Openness to business Logic
● Split Traffic. Canary Deployment!
● No Vendor Lock-in
● OMG! No, You don’t need to know Kubernetes!
● Bring your own runtime, Use any language of your choice
The Good Parts
So much Talk!
Let’s Invoke The Demo Gods
The Future of Serverless
“We need to adopt Serverless Containers as the beneﬁts are
enormous. We are not there yet but on the way. Rethinking the way
we deploy apps with Serverless is happening and we just
scratched the surface.”
you! Obinna Odirionye