Why the fuss about serverless
summary
Argues serverless is a shift of compute from product to utility, creating low MTTR environments that enable functional billing and new operating practices; shows a reproducible mapping method (anchor user, position, movement) as a value chain plus evolution map and claims ~30 economic patterns, ~40 doctrines and 600 pages of material; recounts building Zimki/Zemke (full JavaScript front/back PaaS, launched 2007) and explains why APIs only work reliably on industrialized components.
AI-written summary · about
chapters (10)
- 0:00Intro
- 7:15Why
- 8:19Situational Awareness
- 16:26A cup of tea
- 18:56Patterns
- 22:37Principles
- 29:59Ecosystem approach
- 31:15Circular path
- 32:54History of computing
- 35:43End of cloud
related talks
41mWhy the fuss about serverless
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
25mA Decade of Modern JS and the Rise of Serverless Fullstack
28mServerless - the way microservices should be
01h 00mMicroservices and Serverless
46mServerless: Making Sense with a Cloud Paradox
04mWhat if serverless was real?
51mConfusion In The Land Of The Serverless