Development productivity in a post serverless world
summary
A power cut breaks a lone auth server called Argo, it gets unplugged, ridden home on a scooter and plugged back in so the service immediately restores — a concrete example that hardware matters. The claim is that traditional infrastructure as code (separate YAML, CloudFormation/Terraform) won’t win the next 5–10 years; instead platform as code unifies infra and app in a single CI/CD pipeline and single language. Docker, Kubernetes and Helm drove earlier convergence; serverless framework and Lambda still keep infra and function code split.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 3:41From physical servers to serverless
- 8:14Docker and containerization shift
- 10:18The plateau of serverless productivity
- 12:44Platform as code concept
- 15:10Closing and Q&A
related talks
39mDevelopment productivity in a post serverless world
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
41mWhy the fuss about serverless
01h 00mMicroservices and Serverless
04mWhat if serverless was real?
41mWhy the fuss about serverless
51mConfusion In The Land Of The Serverless
05mUnleash your DevOps with Serverless
