What if serverless was real?
summary
Argues that handing scaling to Amazon and Google shifts where product value and careers live, citing Mike Roberts' common reaction of what are we giving up and Deepak Singh's quip calling AWS Lambda modern-day Perl. Claims resistance comes from control bias, fear of lost enterprise value for SaaS/infrastructure startups, and engineers enjoying poking at leaky abstractions. Says serverless is not just functions or stateless glue but a platform-level tradeoff that actually works for many complex systems.
AI-written summary · about
chapters (3)
- 0:00Psychological resistance to serverless
- 1:20Overcoming resistance to serverless
- 2:54What is serverless
related talks
51mConfusion In The Land Of The Serverless
01h 00mMicroservices and Serverless
55mConfusion In The Land Of The Serverless
53mServerless is the Abstraction We Deserve
14mThinking Twice About Migrating to Serverless
35mServerless Experiences -- On Your Own Servers?
27mSite Reliability in the Serverless Age
41mWhy the fuss about serverless
