Flink in Zalando's World of Microservices
summary
Zalando builds Saiki, a Kafka-backed data integration layer on AWS that funnels thousands of event types into Flink jobs running on EC2/Docker, materializing results into Elasticsearch and CSV files fetched by Oracle via a REST exporter. Flink wins over Spark for sub-second latency and event-time windows; jobs run sliding windows from one minute to 48 hours, keep large keyed state and open thousands of windows concurrently. Primary uses are business process monitoring (order/delivery velocities, alerts) and streaming ETL to pre-aggregate and offload the monolithic data warehouse.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:11Zalando overview
- 2:38Old BI architecture
- 4:24Radical agility shift
- 6:55Event bus with Kafka
- 8:00Sick team and Flink setup
- 11:57Flink in microservices
- 13:20Stream processing choice
- 15:10Spark vs Flink comparison
- 18:43Flink deployment setup
- 19:49Business process monitoring
- 23:51Streaming ETL use case
- 27:05Future Flink use cases
- 31:26Conclusion and Q&A
related talks
22mData integration in the world of microservices
41mBeyond the Hype: When Apache Flink Solves Real Problems
40mFrom concept to production; the fastest way to develop & deploy Apache Flink jobs
46mFlink SQL in 2020: Time to show off!
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
30mBuild and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics
21mFlink's application at Didi
47mBring Flink to Large Scale Production
