Event-driven serverless architectures using Knative and Cloud Run.
summary
Knative Serving deploys containers with auto-scales to zero after 60s, revision names and traffic splitting; Knative Eventing uses CloudEvents, a broker + triggers for filtering, and channels (demo uses in-memory, production uses Kafka or Push subscription). Demo wires Cloud Scheduler → BigQuery (public COVID dataset) → temporary table → chart creator → Cloud Storage → notifier (SendGrid) and sends a daily email; everything runs end-to-end and is reproducible from the GitHub examples.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:12Overview
- 2:57Serverless
- 4:50Containers
- 6:04Serverless vs containers
- 10:15What is Knative Serving
- 12:20Knative Serving Terminology
- 14:33First Knative service
- 23:03Second Knative service
- 23:55Terminology
- 24:53Cloud Events
- 26:50Broker
- 27:44Trigger
- 28:18Service
- 28:49Channel
- 30:15Messages
- 31:10KtoService
- 32:13Channels
- 33:03Messaging
- 34:04Broker Trigger Delivery
- 35:25Google Cloud Event Sources
- 36:53BigQuery Processing Pipeline
- 40:43BigQuery Code
- 43:33BigQuery Demo
- 46:54Conclusion
related talks
55mEvent-driven serverless architectures using Knative and Cloud Run
52mServerless with Knative
01h 00mEventing with Knative and Cloud Run: From Basics to Advanced
45mServerless with Knative
23mServerless with Knative
55mServerless On Your Own Terms using Knative
35mStop Calling Knative Serverless!
57mServerless with Knative