Billing the cloud: Real world stream processing
summary
Naive cron jobs prove simple but fail under scale, so the billing pipeline uses Kafka stream topics to partition by account, per-minute IP usage and event messages for VM create/scale/stop, and a hybrid approach: consumers keep in-memory state and apply hourly inventory snapshots for reconciliation. Usage records commit only after billing writes, via manual offset commits, preventing overbilling while tolerating short gaps; system runs with low ops cost and already powers DNS and log pipelines.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:40Business Model
- 10:51Drawbacks
- 17:47Operational simplicity
- 18:37Integration
- 27:06Process crashes
- 27:30Reconciliation
- 28:52Avoiding double billing
- 32:19Looking back
- 33:28What about batch
related talks
31mBridge to the Cloud
32mShould you read Kafka as a stream or in batch? Should you even care?
39mUsing Streaming Data Pipelines in the Cloud to Achieve Success
32mScaling your Kafka streaming pipeline....
22mVideo Access-Log Processing with Apache Flink
31mHelp I need a stream processor - learning how to chose ...
24mHow we Attributed Cost Per Tenant in a Kubernetes Environment
43m800 mio. IP addresses to coordinates using Kafka Streams #bbuzz
