Enriching your Data Stream Asynchronously with Apache Flink
summary
Shows how to replace blocking lookups with Flink’s async I O using RichAsyncFunction and demonstrates it running on Amazon Kinesis Data Analytics for Apache Flink. Demo calls an API Gateway + Lambda that sleeps 1.5s and proves async throughput scales as capacity goes from 1→2→4 doubling records/sec, while synchronous map stalls. Covers emitter thread, ordered vs unordered emit, timeout and capacity tuning, open/close for shared connections, RocksDB incremental checkpoints to S3 and CloudWatch metrics and autoscaling behavior.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:00Use Cases
- 2:42Design Considerations
- 5:33Synchronous vs Asynchronous
- 6:38Why is Asynchronous Important
- 8:15Asynchronous IO Architecture
- 18:27Demo
related talks
51mStream Processing Smackdown: Kafka Streams vs. Apache Flink
42mStream Processing with Apache Flink
39mEvaluating Streaming Framework Performance for a Large-Scale...
41mStream Processor as a Database: Building Online Applications
40mThe Seven Deadly Sins of Streaming
20mBatching vs. Streaming - Scale & Process Millions of Measurements a Second
23mBetter, Faster, Stronger Streaming: Your First Dive into Flink SQL
40mReal-time Customer Engagement in Gaming Using Kafka and Flink
