An open-source system for data streaming in which a broker queues and persists data records (also called events or messages) between sources (publishers) and targets (subscribers). Sequences of these records are sorted into streams called topics.
Added Perspectives
What the experts say.
In a nutshell, Kafka “producers” publish data records to brokers that persist those records to file systems on disk until they are read – either real-time or later on – by “consumers.” Records are divided into topics (a.k.a. streams) to which consumers can subscribe for selected use. Topics also can be partitioned to improve throughput via parallel consumption and enable redundancy via partition replicas across multiple clustered brokers. Here is a sample architecture for one topic. While this shows multiple examples of producers, one topic often maps to a single producer.
Relevant Content
Keep reading.
Blog
Applying the ACID Test to Apache Kafka
Nov 06, 2018 - With Kafka, enterprises can address new advanced analytics use cases. But does it displace data architecture pillars, such as the database?
Blog
Why and How Data Engineers Realize DataOps Benefits with Apache Kafka Streaming
Sep 06, 2019 - Learn how to achieve the DataOps objectives of improved efficiency and data quality by migrating to a streaming architecture based on Apache Kafka.
Browse the Glossary
Look up a term.
- 0..9
- A
- B
- C
- D
- E
- F
- G
- H
- I
- J
- K
- L
- M
- N
- O
- P
- Q
- R
- S
- T
- U
- V
- W
- X
- Y
- Z
Talk To Us
Let's build your data strategy.
Tell us where your data is today, and we will show you the climb from here. Based in Denver, working with teams everywhere.