A Materialization Engine for Data Integration with Flink
summary
A Flink-backed engine reads topic partitions from Nakata (Kafka), deploys one short-lived batch job per request via Flink’s REST API, and writes per-partition files to EBS then S3 while transforming nested event JSON into flat CSV according to JSON→CSV mappings stored in ZooKeeper. Jobs use a stoppable source and expose custom accumulators for progress; a session-window compaction by partition key and ordering key reduces stream size (up to ~70%), leaves out-of-order corrections in separate files, and simplifies operational stack and ingestion into relational warehouses.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:06Architecture
- 3:46Data Integration
- 4:59Materialization Engine
- 7:13Flink Backend
- 11:06Stream Compaction
- 14:37What we gained
- 16:43Questions
related talks
40mFrom concept to production; the fastest way to develop & deploy Apache Flink jobs
31mFlink @WORKDAY: scaling of ingestion data pipelines to S3
43mA Data Streaming Architecture with Apache Flink #bbuzz
40mFlink in Zalando's World of Microservices
42mApache Flink deep-dive #bbuzz
30mBuild and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics
51mStream Processing Smackdown: Kafka Streams vs. Apache Flink
34mBeaming Flink to the Cloud @ Netflix
