Your API needs to operate on the worldwide edge
summary
Shows an ATM locator demo built with Cloudflare D1 and an edge function, claims raw D1 queries take ~830–1,300 ms while edge caching cuts responses to ~25–70 ms, and demonstrates caching at the CDN layer (Zone cache) to beat a 90 ms baseline. Explains tradeoffs: edge runtime JS/WASM limits, database proximity, connection exhaustion, and mitigations like DB proxy (Prisma Accelerate / RDS Proxy) and global replicas with concrete timings and a working demo.
AI-written summary · about
chapters (9)
- 0:00Introduction and Overview
- 1:00Speaker Introduction and Audience Relevance
- 2:19Understanding the Edge
- 6:14Edge Runtime and Tradeoffs
- 7:53Database Considerations for Edge Computing
- 13:51Why Deploy APIs to the Edge
- 19:48Demo: Building an Edge API
- 25:50Debugging and Performance Optimization
- 32:14Conclusion and Q&A
related talks
28mWe Live in Memory: Making Λ and GraphQL Respond in 70MS
24mDatabase Access on the Edge with Cloudflare Workers & Prisma
01h 00mYou Sell Caches? No, We Just Show Them
46mEdge Performance with In memory NoSQL
39mEdge Compute Infrastructure for Experience Business
57mDSS Keynote — Back to the Future: Prepare Your Data Infrastructure for Anything
10mData that scales: from modern frontends to the Edge
48mEdgeLake: Extending the Cloud to the Edge – an LF Edge Project