Stateful Web Service: A Distributed Lambda Function for Client-Server Interactions
summary
Meta builds a stateful engine called BladeRunner that emulates long‑lived PHP services by keeping connections and subscriptions in a stateful process while running product logic as PHP lambdas that receive events, lambdas, actions and return compact actions for BladeRunner to execute. It separates infra and product code, enables subscriptions, timers and client log batching, reduces resource contention and attribution issues, and already powers thousands of products (SOSP 2021 paper + upcoming blog).
AI-written summary · about
chapters (11)
- 0:00Start
- 4:57Infra & Product Logic Blend
- 6:35Product logic categories
- 7:19Separation of product logic from platform
- 9:19Selection of product development Environment
- 10:12Realistic view of PHP Servers
- 11:12Dream of a Stateful PHP Server
- 13:11Events, Lambdas & Actions
- 16:26Blade Runner feature offerings
- 17:10Bladerunner as a caching layer
- 18:53Conclusion
related talks
46mServerless Application on PHP
01h 03mServerless PHP: how does it really work?
44mServerless PHP applications with Bref
58mPHP on Lambda with Custom Runtimes
27mStateful Functions 3.0: Towards a Cross-Platform Stateful Serverless Stack
29mMicroservices in Your Monolith
39mServerless PHP applications with Bref
56mRunning Your PHP Site on AWS Lambda