Containers and AWS Lambda: Choose the optimal compute for applications
summary
AWS compares Lambda, ECS, EKS, Fargate, App Runner and Proton with concrete claims and examples: Lambda has over 200 event sources and bills by the millisecond; Lego rearchitects checkout into event-driven Lambdas and stabilizes Black Friday traffic; Coca‑Cola deploys a QR touchless flow to 30,000 machines in 100 days using serverless; Fargate removes instance management, App Runner builds and runs web apps from code, and Proton manages templates for large fleets. Two‑thirds of industry containers run on AWS and 80% of container customers also use Lambda.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:20Abstract away the infrastructure pain
- 3:16Business drivers for migrating to AWS services
- 4:27Computing in modern applications
- 6:43Similarities in approaches
- 7:39Differences in approaches
- 9:11Most customers use a combination
- 10:00Common use cases
- 11:40Why customers choose Lambda
- 13:23What does serverless mean?
- 16:58Lego uses an event-driven design for scalability
- 20:48Why customers choose container services
- 22:15How much do you want to manage?
- 24:38No boundaries: Run containers where you like
- 25:29AWS App Runner: Container application service
- 27:31AWS Proton: Consistent code pipeline standards
- 29:12Modern application computing services landscape
- 29:46T-Mobile uses both containers and Lambda
- 30:46Taking the next step
related talks
35mContainers and AWS Lambda: Choosing optimal compute for modern apps
41mContainers or Serverless Functions - When to choose what?
51mServerless Compute at the Heart of Your EDA
53mContainers and Serverless with AWS
40mServerless Compute at the Heart of Your EDA
47mServerless Compute at the Heart of Your EDA
47mReal Use Cases for Using AWS Lambda for Infrastructure Tasks
01h 01mYou have a container image: Now what?