Serverless for Data Scientists
summary
Claim: serverless removes OS management so data science runs as short-lived functions. Demonstrations use AWS Lambda with deployment via Zappa and parallel mapping with pi r n. Surprises: an Instapaper migration drops $10,000/mo to $370/mo, a embarrassingly parallel Black Scholes run shows ~270× speedup, and cold-starts add ~20s overhead. Built artifacts: cron bots and a Flask model server that downloads a pickled classifier from S3 and works within Lambda limits (≈1.5 GB RAM, 15 min timeout).
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:09Move to cloud and serverless
- 3:58What is serverless
- 7:29Deploy web app serverless
- 11:19Serverless cron jobs
- 14:51Advantages and disadvantages of serverless
- 17:43Data science use cases
- 20:31Introducing PyRone
- 24:45Embarrassingly parallel
- 26:08Real-world examples
- 30:18Hyperparameter optimization
- 35:56Summary
- 39:45When serverless fails
- 40:51Q&A
related talks
01h 00mServerless - reality or BS - notes from the trenches
40mThe State of Serverless Computing
47mAdvanced Serverless Architectural Patterns on AWS
54mServerless beyond Functions
02h 37mServerless Deep Dive
24mServerless gives you wings
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
51mServerless - a backend thing that gives superpowers to frontend developers
