Apache Kafka is a distributed event store and stream-processing platform, built at LinkedIn beginning around 2010 and 2011 by a team including Jay Kreps, Neha Narkhede and Jun Rao before the project moved to the Apache Software Foundation. It is designed for unified, high-throughput, low-latency handling of real-time data feeds, organizing records into durable, replicated logs called topics that many independent consumers can read at their own pace. Kafka became a standard piece of infrastructure for event-driven architectures, powering everything from activity tracking to real-time analytics pipelines at large-scale internet companies. This description is adapted from Wikipedia contributors under CC BY-SA 4.0; changes were made. https://creativecommons.org/licenses/by-sa/4.0/
Facts
SignificanceA distributed event-streaming platform built at LinkedIn for high-throughput, low-latency handling of real-time data feeds. 1 FAQs
Why is Apache Kafka named after Franz Kafka?
Jay Kreps named it after the author because it is a system optimized for writing, and he liked his work.
Jay Kreps, one of the people who helped co-create Kafka at LinkedIn, chose the name. He picked the author Franz Kafka because Kafka is described as a system optimized for writing, and he liked the author's work.
Connections
In the Other Atlases
Developed By
Also in Business Atlas: the developer of this subject.
Sources
1. Wikipedia: Apache Kafka
Wikimedia FoundationLead section
Apache Kafka is a distributed event store and stream-processing platform. It is an open-source system developed by the Apache Software Foundation written in Java and Scala.
Lead sentence
Apache Kafka is a distributed event store and stream-processing platform.
In Group: Distributed Data Processing Infrastructure, Lead
Apache Kafka is a distributed event store and stream-processing platform.
View the Source 2. Wikidata: Apache Kafka
- Wikidata Q16235208, resolved via en.wikipedia pageprops (wave rule R-L)
- Wikidata Q16235208 P275 (license)
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.