Cloud functions provide a serverless computing model that charges users only for the resources consumed by their code, eliminating the need to manage and scale servers. This on-demand model allows developers to focus on coding without worrying about operational concerns like scaling, monitoring, or versioning. While serverless computing has limitations like potential latency issues and a lack of strong service level agreements, it presents opportunities to rethink traditional practices and billing models for building and delivering digital services.

1. Serverless
JavaScriptGojko Adzic @gojkoadzic https://gojko.net

2. Cloud functions
are the most revolutionary
improvement since EC2

3. Billing actual usage,
not reserved capacity
→ $0.0000002 per request
→ $0.000000834 for 100ms @ 512MB
→ First 1 million requests per month are free

4. It's code with
batteries included

5. No need to worry about...
→ Scaling
→ Monitoring
→ Recovery
→ Versioning
→ Logging

6. Give the platform
traditional server roles
→ Gatekeeper ➤ Distributed Auth
→ Scaling point ➤ Containers
→ Orchestration ➤ Client or workflow engines

7. "Time to
recover"
no longer important

8. Multi-versioning
is a huge
advantage

9. Weaknesses
→ No strong SLAs yet
→ Latency
→ No PCI compliance
→ No way to keep open connections
→ Requires rethink of common practices
→ Configuration is a challenge

10. Opportunities
→ Skip a generation of tech/process upgrades
→ Rethink operational "best practices"
→ Change billing models
→ Marketplaces for digital services
→ Fine-grained monitoring and optimisation
→ A/B testing throughout

11. claudiajs.com
gojko.net