Unlocking New API Opportunities: PaaS to RPC Migration
summary
Claims that migrating from PaaS-style HTTP APIs to RPC and machine-to-machine streams RPC reduces traffic by returning only needed fields and enables server-side calculation and DDD-style data ownership. Proposes replacing ID-limited filters with vector search using approximate nearest neighbor for per-customer deal ranking, adds an advanced consensus point for eventual consistency instead of stepwise locking, and suggests personal assistants hold private PII to enable declarative requests (food delivery, travel bundles) while shifting security to trusted client platforms.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:38Future of API
- 1:46Whats wrong with current API
- 4:08Open search principles
- 5:23Client API
- 7:24RPC
- 9:35Security changes
- 11:47Practice examples
- 15:04Personal assistance
- 16:54Conclusion
related talks
38mAdvanced API Design for Scalable Distributed Systems
31mRPC Frameworks Overview
28mBetter APIs through Better More Timely Data
27mSecuring the AI Revolution - [...]
01h 01mAn Architect's Approach to API Strategies
01h 01mRPC is Evil
26mServing Data as API
27mStrategies to Deliver Contextual API Experience