Serverless Python in the real world: common patterns & challenges
summary
Built a serverless URL shortener that records clicks and redirects, deployed on AWS Lambda + API Gateway using frameworks like Serverless and Zappa (Flask adaptor). Load tests up to ~1,000 concurrent invocations show latency spikes after ~250 concurrent cold starts; packaging native binaries required Docker builds to avoid runtime failures. Hitting Postgres connection limits forces either a proxy like pgbouncer or a switch to Aurora Serverless / queueing (SQS). Pricing note: first million Lambda invocations free, then roughly $0.20 per million — works for bursty loads, not sustained high throughput.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 7:04Product overview
- 10:18AWS Lambda basics
- 13:33Scalability and dependencies
- 17:09Zappa framework solution
- 21:37Binary system challenges
- 24:36Testing and error handling
- 28:52Monitoring and logging
- 31:50Local testing and mocking
- 34:24When to use serverless
- 36:12Serverless ideology
- 38:30Q&A
related talks
31mA quick intro to AWS Serverless
34mPython in Serverless Architectures
19mBuilding Serverless API Backends
54mServerless Python on AWS Lambda using the Serverless Framework
01h 00mServerless - reality or BS - notes from the trenches
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
29m2 Years, 0 Servers: Lessons learned from running a startup 100% on Serverless
25mA Crash Course on Serverless Applications in Python
