The API is the Platform
summary
Postman’s early serverless stack runs into zero observability and flaky behavior—an internal reliable messaging service proves neither reliable nor testable—so the team mandates every Lambda to expose an API and live in a Postman collection. That shift forces retirement of many ad‑hoc functions, surfaces misfit compute, and leads to moving core workloads to containers on Elastic Beanstalk as a step toward Kubernetes. The central claim: design around APIs as the system surface, because AI agents and autonomous callers consume discoverable APIs, not raw functions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 6:41Serverless
- 9:07Reliable messaging service
- 12:02We misread the promise and paid the price
- 16:35Reality check
- 20:55Shift in lens
- 24:08Interface-driven serverless
- 24:54Future with AI
- 26:04Reclaiming the dream
- 27:54Outro
related talks
30mPostman Platform Overview: Be API-First, Not API-Last
35mThe Future of APIs: Postman's Founder Speaks
22mRevolutionizing API development: Collaborative workflows with Postman
26mCollaborate Like You Mean it: The End of Siloed API Development
35mMastering API Ops: Build Scalable Applications
29mFull API Lifecycle Management
17mAPI Testing Unlocked
23mAPIs at Scale for a Great Developer Experience