Boxcars and Cabooses: When one more XHR is too much
summary
Salesforce shows that bundling XHRs cuts API chatter: their REST data API handles ~4 billion transactions/day and adds a composite batch endpoint that packs multiple HTTP calls into one and returns per-subrequest status codes (defaults to continue on subrequest failure but can halt on error), plus a composite tree endpoint that creates parent and nested child records atomically (up to 200 records total) and demos succeed. Client-side queuing uses the Action Service and Caboose to coalesce requests; offline storage relies on SQLCipher encryption.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:50Salesforce
- 2:19Heroku
- 3:52Multitenant architecture
- 6:07API
- 6:21API Architecture
- 7:46Data APIs
- 8:52The importance of APIs
- 11:08Sample API interactions
- 12:52Too many trips
- 13:10Bundle requests
- 13:56Batch Composite
- 14:19Batch Composite Example
- 15:15Batch Composite Behavior
- 16:11Enterprise Data
- 16:51Parent Data
- 18:58Demo
- 26:32Clientbased framework
- 26:58Aura
- 27:18Moving things forward
- 28:17Three blind developers
- 28:30Action Service
- 28:58Deferring Transactions
- 29:34Apex API
- 30:46Offline access
- 31:32Questions
related talks
15mAPI Development Collaboration at Scale - Challenge and Solutions
37mScaling Rails for Black Friday and Cyber Monday
25m5 ways to make your integration more resilient
29mHow We Reliably Send a Million Messages Per Request
28mFrom Backend Powerhouses to Web-Friendly APIs: Unlocking
30mEric Baer - SeattleJS Conference 2017
38mAdvanced API Design for Scalable Distributed Systems
17mManaging Performance in a Hybrid SPA