The Future of Serverless
summary
Serverless claims are concrete: over 1 million monthly active Lambda customers and 10 trillion invocations per month, Lambda begins as an S3 processor and now adds 2025 features like remote IDE debugging. The stack strategy harmonizes payloads and throttles, adds workflow primitives for agentic patterns, and exposes functions as tools via MCP integration so non‑deterministic agents call serverless tools without capacity planning. Advice is explicit: prototype now, measure event‑driven outcomes.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:48What is serverless?
- 4:35Why serverless?
- 6:32Pioneering serverless compute
- 8:25Event-driven architectures
- 13:13AI agents
- 14:51Agentic or serverless?
- 22:06What are we doing to help build for the future?
- 26:26Start now
- 27:32Outro
related talks
48mThe future will be Serverless
31mThe Evolution of Serverless: Past, Present and Future
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
20mWhy Serverless Architecture is Changing Software Development
49mThe Past, Present, and Future of Serverless
40mWho Needs Serverless?
12mServerless State of the Union
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
