Why the fuss about serverless

on YouTube ↗41m

" summary

Argues serverless (Lambda) shifts compute from product to utility, dropping MTTR and forcing new architecture and ops practices that make functional billing meaningful and reveal real code cost. Describes building a JavaScript full-stack PaaS called Zemke in 2007 that let teams write front and back in one language, grew fast but was killed by a parent-company decision, and shows how APIs + industrialized components create ecosystems where JavaScript front and back-end and serverless enable tiny, focused services to scale.

AI-written summary · about

" chapters (10)

1. 0:00Intro
2. 7:15Why
3. 8:19Situational Awareness
4. 16:26A cup of tea
5. 18:56Patterns
6. 22:37Principles
7. 29:59Ecosystem approach
8. 31:15Circular path
9. 32:54History of computing
10. 35:43End of cloud

" related talks

• 41mWhy the fuss about serverlessSimon Wardley · International Javascript Conference 2018 London
• 28mServerless - the way microservices should beIvan Jovanovic · OdessaJS 2018
• 25mA Decade of Modern JS and the Rise of Serverless FullstackBrian LeRoux · CascadiaJS 2024
• 58mServerless - the brief past, the bewildering present, and the beautiful (?) futureMike Roberts · NDC London 2018
• 20mWhy Serverless Architecture is Changing Software DevelopmentDavid Wells · Reactathon 2018
• 04mWhat if serverless was real?Nick Rockwell · O'Reilly Velocity Conference 2017 - New York, New York
• 44mServerless: Giving superpowers to frontend developersAleksandar Simovic · Armada JS 2019
• 51mConfusion In The Land Of The ServerlessSam Newman · JavaDay Ukraine 2017