Unifying streaming and message queue with Apache Kafka
summary
Uber builds a message-queue layer on Apache Kafka that adds dead letter queues, ack/nack out-of-order with configurable retries and delay, and in-process fanout so consumers can parallelize without blocking Kafka commits. The system handles tens of petabytes and tens of thousands of topics, preserves offsets for cross-DC failover, replicates topics via an in-house replicator, and exposes simple language-agnostic handler APIs so Java/Python services can redeliver, purge, or requeue failed messages.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:30Agenda
- 2:05Use Cases in Scale
- 2:43Use Cases
- 17:36Reliability
- 18:07Cost Efficiency
- 27:26Future Work
- 41:02How Do We Deal with Duplicate Data on Kafka
- 41:52End Users Deal with Duplicates
related talks
48mKafka as a Message Queue: can you do it, and should you do it?
30mEvent Streaming and the Future of Applications
50mIntroduction to Apache Kafka
55mDemystifying Stream Processing with Apache Kafka
53mDemystifying Kafka
41mApache Kafka simply explained
45mAdvanced Kafka Features: From Dynamic Consumers to Fault Tolerance
01h 31mDeveloping Real-Time Data Pipelines with Apache Kafka
