Five rules for super-responsive serverless apps
summary
Five concrete rules: measure, don’t trust docs — test edge vs regional endpoints yourself; cut cold-start time (modern Lambdas start in ~10–20 ms) and enable HTTP keep‑alive for SDK clients; cache the context so instances reuse connections; deploy close to customers — regional calls can be ~37 ms end‑to‑end vs ~100 ms from the US, direct invokes hit ~18–30 ms; avoid using provisioned concurrency for orchestration, static files or data movement — use CloudFront, S3 direct uploads and Cognito signatures instead.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:37Test the "Truth" Don't trust anything you read online, especially if older than a few months!
- 13:41Start speedily Focus on time to start, and the rest becomes very simple!
- 18:43Cache the Context Lambda isn't actually stateless, avoid re-initialisation when you can
- 22:33Come to customers Place workloads close to your users.
- 27:56Drop delegation Use Lambda to compute and transform, not to secure or transport
related talks
43mBest Practices for Serverless Developers
35mEfficiency of Serverless Architectures with AWS Solutions
44mApplying principles of chaos engineering to serverless
19m(N+1) Lessons I learned about serverless
46mServerless Architecture Patterns and Best Practices
20mThe Serverless First Mindset
35mPatterns for efficient serverless development
40mThe serverless startup