Speaker: Tom Dyson (Wagtail)
There are loads of use cases for very small one-feature websites that just expose one simple function to people. (E.g. some special lookups in publicly available data, reformatting of data, etc).
These simple tools are often written at once, then deployed for a while, then sink into lack of maintenance and are finally taken off.
The fun part is having an idea and writing it. The less fun part is installing an OS, installing your servers, tools, configuring them, making them play with each other, set up DNS, SSL, firewall, backups, and monitoring, and Launch (which is fun again …).
"Serverless" (aka Functions as a Service?)
First off: this is a misnomer. There are still servers behind everything.
All of these platforms have some command line deploy tool, and suddenly your script is available on the internet. Abstraction from containers in the cloud (from VMs in the cloud (from dedicated servers (from owned servers))).
You can now have easy auto scaling (up as well as down) and parallelisation. You can trigger functions with more than just HTTP requests - most platforms interface with logs, S3 uploads, pub/sub, email, and cron.
Serverless platforms encourage better design: "Small pieces, loosely joined" and "write less code".
- AWS Lmabda
- Goole Cloud Functions
- Azure Functions
- Serverless Framework (\o/)
- Chalice (least magic)
- now ("like heroku for hipsters")
Common use cases
- Document processing
- Augmenting static sites
- Mobile & JS apps
- Creating APIs
pip install chalice chalice new-project test vim main.py chalice local # debugging chalice deploy
- Shrink your project
- Flatten the bumps (by extracting less than performant stuff to FaaS)
- Move cautiously to microservices
- Consider JAMStack for CMS projects
- Handle more varied events
- Startup times (not below 5 minutes)
- Platforms are not quite mature
- No cost cap
- No persistence