Large Scale User Behavior Analytics by Flink
summary
A real-world UBA pipeline runs Flink as the streaming engine, handles 10k+ unique users across 10+ dimensions, and targets bursts near 100k TPS. CEP logic initially runs in Drools (memory pressure from facts causes failures), so RocksDB-backed Flink state, savepoints and rule-jar hot deploys on Flink 1.4 are used; patterns get grouped or split across jars to avoid thousands of initialized streams, and updates cause only second-scale downtime.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:34Haos background
- 1:18Agenda
- 2:20User Behavior Analytics
- 4:36Challenges
- 6:13Why Flink
- 7:57Architecture
- 10:16Rules Engine
- 11:10Jewels
- 12:43Jewels Pros Cons
- 14:16ETL Needed
- 15:34Hard Deployment
- 16:21Jules Rule
- 18:15Short Term
- 19:37Problems
- 20:46External Key Value Store
- 21:12Time to Live
- 21:51Optimizing Jewels
- 23:03Plan B
- 25:03Workflow
- 27:39Optimization
- 29:09Pros Cons
- 31:08Demo
- 36:54Questions
related talks
45mApache Flink — Real-Time Data Processing
38mStreaming analytics and CEP ... #bbuzz
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
20mBuilding metric platform using Flink for massive scale at Netflix
38mApache Flink: A Very Quick Guide
18mReal-time Experiment Analytics at Pinterest with Apache Flink
34mA journey of scaling high-volume low-latency stateful processing
37mKeynote | Flink Ahead: What Comes After Unified Batch & Streaming?
