Serverless landscape beyond functions

What if serverless wasn't just about functions? See how containers and orchestration have transformed it into the default way to run code in the cloud.

#1about 2 minutes

Defining serverless and its four evolutionary phases

Serverless abstracts infrastructure management, enabling event-driven, stateless services that you only pay for when used, and its history can be understood in four distinct phases.

#2about 2 minutes

Exploring the pre-serverless era with Google App Engine

Google App Engine in 2008 was a precursor to serverless, offering a fully managed platform for web apps but with significant limitations in language support and ecosystem.

#3about 4 minutes

The first wave of serverless with functions as a service

The introduction of AWS Lambda and Google Cloud Functions popularized FaaS but came with challenges like limited triggers, short execution times, and the infamous cold start problem.

#4about 8 minutes

How serverless containers improved flexibility and performance

Serverless container platforms like Google Cloud Run brought language flexibility, solved the cold start problem with higher concurrency, and enabled better local development workflows.

#5about 6 minutes

Connecting microservices with choreography and orchestration

Services can be connected indirectly via event-driven choreography for loose coupling or managed directly by an orchestrator like Google Workflows for clear, traceable logic.

#6about 3 minutes

Combining patterns for advanced serverless architectures

Advanced architectures often combine event-driven choreography with orchestration and can even integrate serverless workflows with long-running tasks on traditional virtual machines.

#7about 2 minutes

Why serverless is the new default for cloud development

With its maturity in triggers, resources, and orchestration, serverless has become the default, cost-effective, and maintainable approach for running code in the cloud.