Building a serverless PHP Laravel application using Laravel Vapor
summary
Codotto runs a Laravel backend deployed with Laravel Vapor and uses API Gateway to route requests into containerized handlers that invoke AWS Lambda for on-demand execution, RDS with a SQL proxy for the database, S3 for files and SQS for queues. The claim is that this setup scales to millions of requests per minute while cutting costs (team reports ~$80–100/month total), at the expense of harder debugging, 15-minute execution limits and vendor lock-in.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:30Agenda
- 1:33Traditional system architecture
- 6:22Function as a service
- 10:00Use cases
- 13:14Example
related talks
46mOur Experience Migrating Laravel Microservices to AWS Lambda with Vapor
43mDeveloping APIs with Laravel and Serverless on AWS
59mServerless PHP Applications
01h 03mServerless PHP: how does it really work?
57mThe Laravel Ecosystem
56mRunning Your PHP Site on AWS Lambda
02h 08mGoing serverless with PHP and Bref.sh
44mServerless PHP applications with Bref
