Practical Experience Using AWS Lambda in High-Load PHP Applications
summary
A PHP ticketing platform handling ~1.5–2M visits/month moved parts to AWS Lambda using Bref to run PHP 7.2/7.3. The talk covers practical constraints (cold starts requiring warmers, the default 1000 concurrent limit, 250 MB package size cap, and free tier of 1M requests/400 GB‑s), operational tactics (reserved concurrency to avoid 429s), and concrete migrations: analytics via API Gateway, internal calls via ALB, and PDF generation as Lambda functions, yielding reduced ops overhead and cost advantages over EC2 at lower traffic.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 5:22AWS Lambda
- 8:10Use cases
- 13:29Alternatives
- 15:35Cold start problem
- 18:26Avoiding cold start
- 19:30Lambda limits
- 21:59Lambda caching
- 24:26Lambda triggers
- 27:20Step Functions
- 28:45Lambda updates
- 31:13Bref PHP on Lambda
- 33:05Bref deployment
- 34:10Fargate alternative
- 36:42Company experience
- 37:45Future tech
- 38:28Cost efficiency
- 40:15Summary & Q&A
related talks
56mRunning Your PHP Site on AWS Lambda
39mServerless PHP applications with Bref
44mServerless PHP applications with Bref
50mServerless PHP applications with Bref
58mPHP on Lambda with Custom Runtimes
01h 03mServerless PHP: how does it really work?
02h 08mGoing serverless with PHP and Bref.sh
52mPHP on serverless, how it works under the hood