The Nine Use Cases
3 entriesEach use case below pairs a short explanation with the projects and pages you would use to build it.
1. Log Aggregation
2 entriesCollect logs from many applications and services into one durable, central stream for monitoring, troubleshooting and analysis.
2. Change Data Capture (CDC)
3 entriesCapture database inserts, updates and deletes and stream them to warehouses and other downstream systems.
3. Event-Driven Microservices
4 entriesLet independent services such as orders, payments, inventory and notifications communicate through events without tight dependencies.
4. Stream Processing
4 entriesFilter, join, enrich and aggregate events as they arrive, using Kafka Streams or Apache Flink.
5. Real-Time Analytics
3 entriesStream user activity, transactions and operational events into analytics engines for low-latency dashboards.
6. Lakehouse Data Ingestion
4 entriesContinuously load Kafka events into data lakes and lakehouses using Kafka Connect, object storage and table formats such as Apache Iceberg.
7. Fraud Detection
1 entriesProcess financial transactions in real time and feed detection models that flag suspicious behaviour for approval, review or blocking.
8. Buffering and Event Replay
2 entriesAbsorb traffic spikes, decouple producers from slower consumers and replay retained events for recovery or reprocessing.
9. IoT and Telemetry
3 entriesCollect high-volume sensor readings and device events to support alerts, monitoring and historical analysis.
Source
1 entriesThe post that these use cases come from.
Frequently Asked Questions
What is Apache Kafka used for?
Kafka is used to move and store streams of events. Typical uses are log aggregation, change data capture, event-driven microservices, stream processing, real-time analytics, lakehouse ingestion, fraud detection, buffering and replay, and IoT telemetry.
How does Kafka support event replay?
Kafka keeps events in a retained, ordered log, and consumers track their own offsets. A consumer can reset its offset to re-read old events for recovery or reprocessing.
Do I need Flink or Kafka Streams for stream processing?
Either works. Kafka Streams is a library embedded in your application, while Flink is a separate engine that suits larger stateful jobs.
How does Kafka feed a lakehouse?
Kafka Connect sinks or streaming jobs write events to object storage, often as Apache Iceberg tables, so lakehouse engines can query them.
How current is this page?
Links were checked in October 2026. The nine use cases follow a public LinkedIn post by Ashish Joshi; the tool descriptions summarize each project's own documentation. Sites that block automated checks are kept and may need a manual click.