Applying the Serverless Mindset to Any Tech Stack
summary
Claim: serverless is a mindset not a specific runtime, and it applies inside any constraint. Uses AWS Lambda and ~30 AWS services with no VMs or containers; built orchestration in functions then migrated parts to AWS Step Functions. Handles iRobot’s scale—millions of robots a year—and absorbs a 100× traffic spike handled as a non-event on Christmas morning where one person only had to increase stream shards. Outcome: much less ops work, engineers shipping features instead of firefighting.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:12Roomba
- 3:25Functions as a Service
- 3:57Managed Services
- 4:38No Ops
- 6:22Customer Value
- 7:31Point of Service
- 8:29Why Serverless
- 9:47Technology
- 12:11Serverless
- 13:47Service Ladder
- 15:36Serverless Mindset
- 16:05Ego is the Enemy
- 16:39Builds SelfService
- 17:27Choosing Serverless
- 18:06Code is a Liability
- 18:38How to best deliver value
- 19:17Selfreflection
- 19:38Minimalism
- 19:57Constraints
- 20:27Hidden Complexity
- 21:44Best Files
- 21:59Service
- 25:33Jared
- 27:33Summary
related talks
28mThe Future of Serverless
19mA Serverless State of Mind
20mThe Serverless First Mindset
20mWhy Serverless Architecture is Changing Software Development
48mThe future will be Serverless
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
12mServerless State of the Union