Interview with Maxim Fateev

on YouTube ↗05m

" summary

Describes building a new messaging system similar to Amazon SQS (to be open sourced) and introducing Apache Flink to get exactly-once semantics for payments and incentives where losing or double-counting a single message is unacceptable. Explains keeping windows for weeks because of very late events and the missing ability to checkpoint into an external database, lists needed features: query state of functions at runtime, dynamic partitioning, safe pipeline upgrades and SQL support for non-programmers.

AI-written summary · about

" chapters (7)

1. 0:00Intro
2. 0:21Projects at Uber
3. 0:55Incentives
4. 1:54Flink
5. 2:21Use cases
6. 3:21Enterprise features
7. 4:17Tips

" related talks

• 49mscale.bythebay.io: Stephan Ewen, Apache Flink and the Next Wave of Stream Processing ApplicationsStephan Ewen · Scale By the Bay 2017
• 41mBeyond the Hype: When Apache Flink Solves Real ProblemsNaci Simsek · Berlin Buzzwords 2026
• 37mKeynote | Flink Ahead: What Comes After Unified Batch & Streaming?Stephan Ewen · Flink Forward Global Virtual 2020
• 43mLeverage the power and simplicity of SQL on Apache FlinkFabian Hueske · Berlin Buzzwords 2018
• 38mApache Flink: A Very Quick GuideVladimir Bacvanski · Data By the Bay 2016
• 45mBuilding an Event-Driven Application with Apache FlinkDaniil Tulikov · Joker 2024
• 35mApache Flink 2.0: Unified Enterprise Data Processing System and BeyondBowen Li · Scale By The Bay 2019
• 04mInterviewJie Ren · Scale By The Bay 2018