Measuring and increasing developer productivity with the help of Serverless
summary
Argues that AWS Serverless (Lambda, API Gateway, DynamoDB, EventBridge, Step Functions, Amplify) actually raises developer productivity by cutting code, ops and tech debt: example of API Gateway→DynamoDB ID generation eliminates a lambda; canary rollouts use canary Lambda aliases and SAM/SAM-like deployments with automatic alarms and rollbacks; visual Step Functions and Amplify speed workflows. Claims teams spend 75% maintenance/25% development, sees faster deploy cadence (monthly → several times per day) and easier scaling for Christmas traffic spikes, but warns of cost and runtime upgrade responsibilities.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:00Three types of intrinsic cognitive load
- 5:35What is holding us back
- 8:45Legacy systems
- 10:40What is Serverless
- 16:15What is the commodity utility
- 17:30How to measure the success
- 22:10Persistence
- 25:10DevOps
- 28:40How to write
- 29:10Why write less code
- 30:40Service integration
- 35:35Common patterns
- 37:35Reducing dependencies
- 39:05Conclusion
- 40:35Questions
related talks
31mAccelerate business innovation with serverless applications
36mTransforming SaaS with Serverless Architectures
25mLeveraging Serverless in Full-stack Development
30mEvolving Serverless Architectures
51mTaking Serverless to the Next Level
42mBest practices for serverless developers
25mHow Serverless Is Changing the World for Developers
42mAWS Lambda from the trenches