Containers vs Serverless from a DevOps standpoint
summary
Compares managing containers versus FaaS with a simple Node.js app and gives concrete tradeoffs: containers use Docker, a Dockerfile, image repo and Kubernetes and require about eight distinct deploy steps (build, push, pull, apply), giving full control, easy debugging and a path to migrate monoliths and long‑running jobs. Serverless uses AWS Lambda or Fargate with the Serverless Framework, deploys with one CLI command to configure events and push functions, auto‑scales, bills per invocation (example 200 ms) but has time limits (≈5 minutes) and weaker observability.
AI-written summary · about
chapters (6)
- 0:00Introduction and agenda
- 2:22Understanding containers
- 7:13Understanding serverless
- 11:46Deployment process comparison
- 15:37Verdict and summary
- 16:50Q&A session
related talks
35mContainer vs. Serverless: The Good, the Bad and the Ugly
41mContainers or Serverless Functions - When to choose what?
51mWho needs containers in a serverless world?
44mServerless and containers are coming together: an AWS perspective
06mAn introduction to serverless
58mServerless Under the Hood
01h 00mMicroservices and Serverless
41mIs Serverless the End of Kubernetes?