Serverless Kafka Patterns.
summary
Practical patterns for marrying Kafka with AWS serverless: use API Gateway + Lambda to write to Kafka instead of always running containers; use RDS triggers or Lambda for CDC as an alternative to 24/7 Kafka Connect workers; run consumers as Lambda functions that call partner HTTP APIs; offload topics to S3 via Lambda for cheap archival. MSK Serverless fits short‑lived test clusters and feature branches. Start serverless for low traffic (examples as low as $5–$10/month) and move to provisioned capacity once throughput and predictability demand it.
AI-written summary · about
chapters (15)
- 0:00Introduction to serverless Kafka
- 3:25Classical distributed streaming systems
- 10:38Total cost of ownership in cloud
- 17:00AWS serverless expertise tiers
- 21:17When serverless doesn't fit
- 25:11API to Kafka with serverless
- 27:24Database changes to Kafka
- 30:15Message broker to Kafka adapters
- 32:20Kafka to external HTTP APIs
- 34:06Archiving Kafka data to S3
- 36:15Kafka Connect serverless patterns
- 37:40Serverless Kafka clusters
- 39:47Lessons learned from serverless
- 43:21Measure before you optimize
- 45:06Summary and Q&A
related talks
49mServerless Architectural Patterns and Best Practices
51mServerless architectural patterns
12mServerless Stream Processing with Confluent Cloud, Kafka and AWS Lambda
48mServerless design patterns
55mServerless Design Patterns for the Enterprise with AWS Lambda
01h 02mServerless Architecture Patterns
40mCloud architecture patterns, how to implement them in a serverless way
28mBuilding Event Streaming Applications with Serverless Kafka
