The Ops in Serverless

on YouTube ↗15m

" summary

Argues that serverless lowers provisioning work but raises operational complexity and so requires deliberate governance, CI/CD and instrumentation. Notes a real AWS case where a stub function app randomly fails then continuously fails and CloudWatch’s duration, error and throttle metrics prove insufficient for debugging. Calls out common problems: function rot leaving orphaned, cost-driving functions, undocumented console-deployed lambdas, service limits and missing visibility, and recommends embedding identity and permissions in code via a serverless framework.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and background
2. 0:44Lessons from gaming
3. 2:46Operations and complexity
4. 4:54Serverless considerations
5. 7:31Operational burden and scale
6. 8:42Governance and discovery
7. 11:48Monitoring and observability

" related talks

• 49mYou Don't Want ServerlessErik Onarheim · NDC Oslo 2024
• 55mConfusion In The Land Of The ServerlessSam Newman · NDC Oslo 2017
• 40mDevOps in the era of serverless computingAlessandro Vozza · Codemotion Amsterdam 2017
• 29mHow is the role of DevOps changing in a Serverless environment?Jeremy Edberg · devopsdays Chicago 2016
• 27mSite Reliability in the Serverless AgeErik Peterson · DevOpsDays Boston 2018
• 03mServerless is other peopleRachel Chalmers · Velocity 2016 New York
• 01h 00mMicroservices and ServerlessSam Newman · NDC DevOps 2020
• 04mWhat if serverless was real?Nick Rockwell · O'Reilly Velocity Conference 2017 - New York, New York