Serverless Containers

Transcript

1. Serverless Containers Jaana B. Dogan jbd@google.com @rakyll
2. @rakyll +
3. @rakyll
4. @rakyll $ supervisor
5. @rakyll $ supervisor
6. @rakyll More managed and abstract Options... IaaS Infrastructure as a Service Networking, storage, physical servers and virtualization are provided as a service. You manage the middlewares, runtime, applications and data. PaaS Platform as a Service Networking, storage, virtualization, security, runtime, middlewares are provided as a service. You manage your applications and data. On-prem On-premises Nothing is managed on behalf of you. You manage the networking, storage, servers, virtualization, middlewares, runtime, your applications and data.
7. @rakyll
8. @rakyll
9. @rakyll “VMs can be great for traditional workloads.”
10. @rakyll “Container orchestration is complex.”
11. @rakyll “Container orchestration is complex.”
12. @rakyll “How can I focus more on my code?” - Developers
13. @rakyll “How can I focus more on my code?” - Developers
14. 01 Pay for usage Scaling down to zero Charging based on usage 02 Autoscaling Scaling based on traffic Scaling up or down fastly 04 Networking Naming SSL support Custom domains Policies 03 Observability Out-of-the-box signals Integration with observability tools
15. @rakyll Cloud Run cloud.google.com/run
16. Cloud Run at a glance • Autoscales based on traffic • Runs in gVisor sandbox • Supports various languages and runtimes service4 service3 service2 service1 users container3 container1 container2 USERS SERVICES CONTAINERS
17. @rakyll Cloud Run Kubernetes CLI or API Cloud Run on GKE One more thing...
18. @rakyll $ gcloud beta run deploy \ --image grpc.io/jblabs/hello \ --cluster gke-cluster-name $ gcloud beta run deploy \ --image grpc.io/jblabs/hello Cloud Run Cloud Run on GKE
19. @rakyll
20. @rakyll
21. @rakyll • Optimized for request based workloads • Optimized for stateless containers • Not optimized for very long running processes • Building block is not a function but a service • gRPC support is in the future • Events and trigger support is in the future Goals and limitations...
22. @rakyll +
23. Thank you Jaana B. Dogan Google jbd@google.com cloud.google.com/run