Real-time Customer Engagement in Gaming Using Kafka and Flink
summary
Real pipeline detail: a game tracks interaction events into Kafka and Flink, evaluates campaigns via a JavaScript filter broadcast through a low‑frequency CRM topic, and writes triggers back to Kafka for the game to act on. The system processes about 1.5 billion events per day, uses broadcast state pattern and per‑player stateful segments, runs a Docker demo and open‑source GitHub repo, and achieves reaction times less than one second while supporting runtime rule updates with broadcast state pattern.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:16Speaker background
- 6:50Stream processing in gaming
- 10:47Kafka architecture
- 17:06Flink basics
- 23:24Customer engagement use case
- 28:44Demo walkthrough
- 36:51Future outlook
- 38:58Closing
related talks
40mReal-time Customer Engagement in Gaming Using Kafka and Flink
42mStream Processing with Apache Flink
38mHow to handle 100k events per second
51mStream Processing Smackdown: Kafka Streams vs. Apache Flink
28mManaging and Scaling Real Time Data Pipelines using Go
20mReal-time analytics with Flink and Druid #bbuzz
41mStream Processor as a Database: Building Online Applications
47mReal-time Fraud Detection Challenges and Solutions
