SPONSOR WORKSHOP / Charlie Engelke/ Google
summary
Claims that serverless code runs only on demand and must keep state in external stores and then demonstrates it by building a working student programming‑contest system using App Engine for the manager site with Identity‑Aware‑Proxy, Cloud Functions for student solutions and many judges, optional Cloud Run for unusual runtimes, Cloud Storage/Firestore for state, and Pub/Sub topics to fan out judging. Slides, runnable demo and code labs exist and the design is exercised end to end.
AI-written summary · about
chapters (9)
- 0:00Introduction to serverless
- 4:44Core design principles
- 8:01Google cloud options
- 13:14Data and event services
- 17:08Simple application architecture
- 22:11Contest system overview
- 27:11Distributed system design
- 34:35Permissions and implementation
- 41:07Conclusion and resources
related talks
02h 05mServerless Python Applications with Google Cloud
43mGoogle Cloud's new serverless features
50mGo Serverless with Google Cloud
34mServerless Computing with Python
43mWhat's new in Google Cloud Serverless
42mNew serverless solutions on Google Cloud for functions, apps and containers
07mServerless: Accelerate your AI
50mA hitchhicker's guide to Serverless computing