Kafka: Building scalable, secure, fast applications.

Photo by Florian Krumm on Unsplash
This is how your system would work if you used Kafka
  1. Broker: Instances of Kafka that commit message exchances are called Brokers.
  2. Topics: Topic are the table equivalent of Kafka systems. All inputs to the systems are stored as part of some topic.
  3. Consumers: The published messages are then used by consumer apps if the consumer has subscribed to the required topic.
Beautiful drawing of a Kafka system, innit?
  1. High Throughput: Kafka can handle some high volume of data.
  2. Fault Tolerant: Clusters are usually fault-tolerant because if a node fails, the other ones take up the load.
  3. Durability: Data is persistent and message replication makes it more durable.
Courtesy: Lourenço, João & Cabral, Bruno & Carreiro, Paulo & Vieira, Marco & Bernardino, Jorge. (2015). Choosing the right NoSQL database for the job: a quality attribute evaluation. Journal of Big Data.
  1. Twitter: Twitter uses Kafka to stream posts, typical pubsub architecture.
  2. Netflix: Event Processing and RT monitoring systems.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Abhinav Srivastava

Abhinav Srivastava

Building: Ignite Tournaments / Former: DeFi Alliance, Persistence, Eth India Co