Serverless Architectures: What, why, why not, and where next?
summary
Positions serverless as two concrete things: backend as a service — vendor-hosted components like Google Firebase (successor to Parse) for databases and off-the-shelf auth such as Auth0 or Amazon Cognito that remove custom plumbing — and functions as a service — deploy single operations as code units that the vendor runs on demand. Functions trigger on events, the platform creates an ephemeral container, executes the function, then tears it down, shifting cost, scaling, and operational responsibility to the platform.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:19Backend-as-a-Service
- 2:09Functions-as-a-Service
- 4:10O'REILLY Software Architecture ENGINEERING THE FUTURE OF SOFTWARE
related talks
06mAn introduction to serverless
53mServerless is the Abstraction We Deserve
43mServerless architectures — approaches to building
35mServerless Experiences -- On Your Own Servers?
42mServerless Landscape Beyond Functions
14mServerless for frontend engineers, in 10 minutes
58mServerless Under the Hood
52mConfusion In The Land Of The Serverless