Serverless PHP Applications
summary
Claims: serverless costs nothing while idle except storage, has cold start latency, enforced time limits (typical <5 minutes), and requires external state. Tools actually used: Apache OpenWhisk, AWS Lambda with Bref and runtime layers (runtime layers arrive 2018), Serverless Framework, Composer, Docker local invoke with Xdebug, PostgreSQL, S3 + CloudFront, Guzzle and AWS SDK. Numbers and examples: Lambda starts 2014, photo site runs every 2 hours, an insurance case sends ~200,000 emails in 6 hours. Built and working: a four-action to-do backend and a 365 photo site that uploads HTML to S3 and invalidates CloudFront.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:22Challenges
- 16:25Action container lifecycle Hosts the user-written code • Controlled via two end points:/init & /run
- 23:06Configure action
- 23:25Configure API Gateway
related talks
44mServerless PHP applications with Bref
50mServerless PHP applications with Bref
01h 03mServerless PHP: how does it really work?
39mServerless PHP applications with Bref
02h 08mGoing serverless with PHP and Bref.sh
56mRunning Your PHP Site on AWS Lambda
58mPHP on Lambda with Custom Runtimes
52mPHP on serverless, how it works under the hood
