Serverless Ops: What to Do / This is What We Do, When the Server Goes Away
summary
Describes replacing host work by wiring cloud services together: take JSON from one API, trigger AWS Lambda via API Gateway, store in DynamoDB, emit events to other functions — a Rube‑Goldberg production deployed to S3/CDN front end. Claims the initial project saves hours but bypasses traditional ops, so operations people must learn to code, run game days, practice chaos engineering, measure cost vs. revenue (FinDev), and join feature/value teams to stay relevant and prove impact.
AI-written summary · about
chapters (5)
- 0:00Start
- 7:25WHAT DOES SERVERLESS MEAN FOR US?
- 7:42GET RID OF YOUR OPS TEAM
- 17:17FINDEV
- 20:39I DON'T WANT TO JUST OPERATE SYSTEMS ANYMORE
related talks
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
32mEmbracing Serverless Ops
51mConfusion In The Land Of The Serverless
29mHow is the role of DevOps changing in a Serverless environment?
28mServerless - the way microservices should be
03mServerless is other people
41mYou Don’t Want to Build a Serverless Monolith
45mPatterns & practices for developing enterprise-scale serverless applications