An introduction to serverless

on YouTube ↗06m

" summary

Serverless splits into two concrete pieces: back-end as a service components like Google Firebase and AWS Cognito that replace databases and auth, and functions as a service where code is deployed as zipped functions/jars. The platform brings up a short-lived container per event (HTTP, S3/object-store changes, message bus, or cron), runs the function, then tears the container down. Claims: no host/process management and faster development, with some operational and cold-start rough edges.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 2:14Functions-as-a-Service (Faas)
3. 2:50Application (process)
4. 4:58Network File System (for file processing, data pipelines)

" related talks

• 04mServerless Architectures: What, why, why not, and where next?Mike Roberts · O'Reilly Software Architecture Conference 2016: San Francisco
• 31mWhat is "Serverless"?Kim Bannerman · Cloud Foundry Summit Europe 2016
• 04mServerless, Revealed!Daniel phrawzty Maher · dotScale 2018
• 52mConfusion In The Land Of The ServerlessSam Newman · NDC Sydney 2017
• 20mWhy Serverless Architecture is Changing Software DevelopmentDavid Wells · Reactathon 2018
• 58mServerless Under the HoodMikhail Shilkov · DotNext 2019 Piter
• 58mServerless - the brief past, the bewildering present, and the beautiful (?) futureMike Roberts · NDC London 2018
• 28mServerless - the way microservices should beIvan Jovanovic · OdessaJS 2018