1. CloudRun:theriseofserverless
andcontainerization
Istanbul December, 2022
Márton Kodok
Google Developer Expert at REEA.net

2. 1. What is Serverless? What are Serverless pain points?
2. Cloud Run: Bringing serverless to containers
3. Build + run
4. Mitigating cold starts
5. Advanced examples
6. Integrating DockerSlim on Cloud Build
7. Conclusions
Agenda
Cloud Run: the rise of serverless and containerization @martonkodok

3. ● Among the Top 3 romanians on Stackoverflow 201k reputation
● Google Developer Expert on Cloud technologies (2016→)
● Champion of Google Cloud Innovators program (2021→)
● Crafting Web/Mobile backends at REEA.net
Articles: martonkodok.medium.com
Twitter: @martonkodok
Slideshare: martonkodok
StackOverflow: pentium10
GitHub: pentium10
Cloud Run: the rise of serverless and containerization @martonkodok
About me

4. Once upon a time
Google Cloud
Functions
AWS
Lambda
Azure
Functions

5. What is Serverless in the Functionsperspective
Cloud Run: the rise of serverless and containerization @martonkodok
Operational
Model
Programming
Model
No Infra Management Managed Security Pay only for usage
Function-based Event-driven Closed

6. Cloud Run
Bringing serverless to containers

7. Containers
Cloud Run: the rise of serverless and containerization @martonkodok
.js .rb .go
.py .sh …
0 1 0
1 0 0
1 1 1
Any language
Any Library
Any Binary
Ecosystem of base images

8. What is Serverless in the CloudRun perspective
Cloud Run: the rise of serverless and containerization @martonkodok
Operational
Model
Programming
Model
No Infra Management Managed Security Pay only for usage
Event-driven Closed
Function-based
Containerized App-service-driven Open

9. Serverless pain points

10. Cloud Run: Pay-per-use
Cloud Run: the rise of serverless and containerization @martonkodok
CPU / Memory / Requests 100ms

11. Cloud Run: Pay-per-use
Cloud Run: the rise of serverless and containerization @martonkodok

12. Cloud Run Managed: Pricing
Cloud Run: the rise of serverless and containerization @martonkodok

13. @martonkodok
Code,
build & run
Part 1

14. Getting started
Cloud Run: the rise of serverless and containerization Image courtesy of @wietsevenema
1. Code (use your entire repo, not just a function)
2. Package (Dockerfile or build-packs)
3. Build image (leverage CloudBuild)
4. Deploy
5. Run + Monitor

15. ChatGPT: create a Python Dockerfile
Cloud Run: the rise of serverless and containerization @martonkodok

16. Build -> Container Image -> Store -> deploy - > Run
Cloud Run: the rise of serverless and containerization

17. Submit + Build
Cloud Run: the rise of serverless and containerization @martonkodok

18. Folder Structure
Cloud Run: the rise of serverless and containerization @martonkodok
cloudbuild.yaml

19. SSL offered out-of-the box + Monitoring Charts
Cloud Run: the rise of serverless and containerization @martonkodok

20. @martonkodok
What about
“cold starts”?
Part #2

21. 1. Use a leaner base image (alpine, distroless, scratch for statically linked binary)
Mitigating cold starts
Cloud Run: the rise of serverless and containerization @martonkodok

22. 1. Use a leaner base image (alpine, distroless, scratch for statically linked binary)
2. Startup CPU-boost
Mitigating cold starts
Cloud Run: the rise of serverless and containerization @martonkodok

23. gcloud beta run services update SERVICE --cpu-boost
gcloud beta run deploy --image IMAGE_URL --cpu-boost
Startup CPU-boost
Cloud Run: the rise of serverless and containerization @martonkodok
CLI

24. 1. Use a leaner base image (alpine, distroless, scratch for statically linked binary)
2. Startup CPU-boost
Mitigating cold starts
Cloud Run: the rise of serverless and containerization @martonkodok
3. Cloud Run: Minimum instances

25. 1. Use a leaner base image (alpine, distroless, scratch for statically linked binary)
2. Startup CPU-boost
Mitigating cold starts
Cloud Run: the rise of serverless and containerization @martonkodok
3. Cloud Run: Minimum instances
4. Always-on CPU
Costs: 10times less than regular price

26. gcloud beta run services update SERVICE --min-instances MIN-VALUE --no-cpu-throttling
gcloud beta run deploy --image IMAGE_URL --min-instances MIN-VALUE --no-cpu-throttling
Minimum Instances & Always On CPU
Cloud Run: the rise of serverless and containerization @martonkodok
CLI
UI

27. Always On CPU Billing
Cloud Run: the rise of serverless and containerization @martonkodok

28. Part #3
Autoscaling

29. 1. When no requests, scales down to 0. (costs savings)
2. Each service can scale by default to 1000 container instances (auto decreases by instance type)
3. Each container instance can handle up to 1000 simultaneous requests (!YAY websockets)
Note: 1000*1000 => 1M simultaneous requests
Autoscaling
Cloud Run: the rise of serverless and containerization @martonkodok

30. 1. FaaS frameworks have fixed concurrency of 1
2. Cloud Run enables you to set concurrency (default 80, can be increased up to 250)
3. Risks! How a free trial experiment ended with a $72,000 bill overnight.
Concurrency
Cloud Run: the rise of serverless and containerization @martonkodok
Common errors:
➔ Uncontrolled retries, Loops (failing tests, missing backoff)
➔ Unwanted traffic (consider using Identity-Aware Proxy, Cloud Endpoint Service)
➔ Reduce concurrency
➔ DDOS (consider using Cloud-Armor, Load Balancer)

31. Cloud Run: Concurrency case study
Cloud Run: the rise of serverless and containerization @martonkodok
Concurrency=1 Clients: 400
Request=3
Concurrency=80 Clients: 400 Request=3
520
instances
150
instances

32. Afternoon talk
Cloud Run: the rise of serverless and containerization @martonkodok

33. Part #4
King of
serverless
compute?

34. Next topics to be covered
Cloud Run: the rise of serverless and containerization @martonkodok
1. Traffic Controls
2. Security
3. Health checks
4. Session affinity
5. SLOs
6. 2nd gen environment
(disk support)

35. Cloud Run: King of Serverless Compute?
Cloud Run: the rise of serverless and containerization @martonkodok
Serverless tools don’t provide canary deployments (subset of traffic)
Allow traffic controls across revisions of a service
Label your revisions for gradual-rollout-strategy (--no-traffic, candidate, latest)
Eg: resulting an automated way to gradually roll out new versions of your Cloud Run services
1/Traffic Controls

36. Cloud Run: King of Serverless Compute?
Cloud Run: the rise of serverless and containerization @martonkodok
Mount secrets from Secret Manager
Binary Authorization for Cloud Run
CMEK - customer-managed encryption keys. (for regulated industries like financial services)
Eg: resulting increased security
2/Security

37. Cloud Run: King of Serverless Compute?
Cloud Run: the rise of serverless and containerization @martonkodok
Configure startupprobes
Configure an HTTP livenessprobe
can configure HTTP, TCP, and gRPC probes
Eg: to determine when a container has started and is ready to accept traffic
3/Container health checks

38. Cloud Run: King of Serverless Compute?
Cloud Run: the rise of serverless and containerization @martonkodok
Configure startupprobes
Configure an HTTP livenessprobe
can configure HTTP, TCP, and gRPC probes
Eg: to determine when a container has started and is ready to accept traffic
3/Container health checks

39. Cloud Run: King of Serverless Compute?
Cloud Run: the rise of serverless and containerization @martonkodok
Session affinity
SLOs (service level objectives)
2nd generation environments (ability to use mounted disk )
Eg: 2nd gen enables network file systems such as NFS, NDB, 9P, CIFS/Samba, and Ceph, as well as Cloud Filestore
4/More recent additions

40. Practical use cases

41. External HTTPs Load Balancer
Cloud Run: the rise of serverless and containerization @martonkodok

42. Multi-Region Load Balancing with Cloud Run
Cloud Run: the rise of serverless and containerization @martonkodok

43. Integrating
docker-slim
Bonus

44. 1. Use a leaner base image (alpine, distroless, scratch for statically linked binary)
2. Startup CPU-boost
Mitigating cold starts + BONUS
Cloud Run: the rise of serverless and containerization @martonkodok
3. Cloud Run: Minimum instances
4. Always-on CPU
5. DockerSlim (minifier, reduce a fat container to slim, more secure as reduces the available attack surface)

45. - is a command line tool
- provides a set of commands (build, xray, lint)
- to reduce the size and optimize your containers.

46. 1. Minify a fat container (reduces the container size)
2. Run a probe to touch all “used”parts
Use DockerSlimas container minifier
Cloud Run: the rise of serverless and containerization @martonkodok
3. Make it more secure (reduces the available attack surface)
4. Faster cold starts
5. Less costs on container build and storage
Note: Good for HTTP based apps. Node.js, Python, Ruby, Java, Golang, Rust, Elixir, and PHP
cmd=build info=results by='5.21X' size.original='413 MB' size.optimized='79 MB' status='MINIFIED'

47. Cloud Build example integration for DockerSlim minify
@martonkodok

48. Article: Integrating DockerSlim on Cloud Build
@martonkodok
https://bit.ly/3iOAShM

49. Conclusion
Cloud Run: the rise of serverless and containerization @martonkodok

50. 1. Simple developer friendly CLI to quickly deploy/manage services without sysadmins
2. Integration with CloudCode, CloudBuildand for continuousdeployments
3. Fast autoscaling - out-of-the-box scaledowntozero
4. HTTPS URLs - out-of-the-box stable HTTPS endpoint - customdomains
5. Enables invocation by HTTP/2, WebSockets and gRPC
6. 2nd gen environment - enables file file storage access natively + but slower cold starts
Enhanced developer experience
Cloud Run: the rise of serverless and containerization @martonkodok

51. Thank you.
Slides available on:
slideshare.net/martonkodok
Reea.net - Integrated web solutions driven by creativity
to deliver projects.