Background Processing, Serverless Style

on YouTube ↗38m

" summary

Serverless claims reduce ops overhead and boost developer productivity by replacing Sidekiq/Resque workers with functions triggered by HTTP gateways, Pub/Sub/SQS queues, or storage events, but it trades opacity and limits for convenience. Examples use S3/Google Cloud Storage, Elasticsearch, ActiveStorage, Pub/Sub and Cloud Functions; Ruby runs on AWS Lambda only. An experiment processes 100M Pub/Sub messages at about 5,000 messages per second with roughly ~0.1% duplicate rate, exposing rate and execution limits and at-least-once semantics.

AI-written summary · about

" chapters (16)

1. 0:00Introduction
2. 0:47About me
3. 1:56Disclaimers
4. 3:32Background Processing
5. 5:17Serverless
6. 11:50Functions as a Service
7. 13:07Webhook Handler
8. 15:45Why would you do this
9. 16:44Text processing
10. 19:03Message queue
11. 20:07Why do this
12. 24:10New YouTube
13. 25:57Spirit of Style
14. 29:08Why Serverless
15. 31:27Things to Know
16. 35:31Additional Resources

" related talks

• 01h 00mServerless Architecture - Tales from a world without serversRobin Weston · NDC London 2017
• 51mServerless architectural patternsYan Cui · NDC Oslo 2018
• 47mServerless in production, an experience reportYan Cui · Build Stuff 2017
• 54mServerless beyond FunctionsDanilo Poccia · Voxxed Days Bucharest 2018
• 31mServerless Rails: Understanding the pros and consDaniel Azuma · RailsConf 2021
• 29mGoing ServerlessSebastien Fabre, Nik Rahmel, Laura Vargo, Eddie O'Rourke, Sebastian Hesse · UXDX Europe 2019
• 42mNo Server Is Better Than No Server: Building Blocks for Serverless ArchitecturesConstantin Gonzalez · code.talks 2017
• 01h 00mServerless - reality or BS - notes from the trenchesLynn Langit · NDC Oslo 2017