Serverless API Gateways for High Scale Systems Performance Cost and Security
summary
Serverless API gateways scale from idle to thousands of concurrent executions and cut infrastructure waste by tuning memory and CPU (examples: fixing memory leaks that caused GC pauses and availability drops), use observability (JMX, bootstrap metrics) to guide concurrency, and mitigate cold starts with container reuse, provisioned concurrency and lightweight dependencies; deploy config-only gateways with edge caching and distributed instances to shave latency; enforce token-based auth, tenant/IP rate limits and zero-trust least-privilege RBAC to survive bursts and attacks.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:11Serverless gateways for scaling
- 4:03Traditional vs serverless scaling
- 7:57Performance optimization
- 11:12Cold start challenges
- 14:00Caching and edge strategies
- 15:26Security for serverless APIs
- 20:22Traffic patterns
- 22:07Key takeaways and closing remarks
related talks
29mBuild highly scalable serverless applications on AWS
42mServerless Tales from the Trenches
54mServerless Architectures: no servers allowed!
43mBest Practices for Serverless Developers
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
42mServerless Landscape Beyond Functions
54mYou should be building Serverless Microservices
54mScaling Web Services for Free to Play