Apache Kafka - a must have tool for distributed toolkit
December 06, 2021

Apache Kafka - a must have tool for distributed toolkit

Jimesh V Shah | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Apache Kafka

My application was dependent on other applications to generate data and those data were needed to be processed immediately. And, processed data were published for other applications. Moreover, data load was very high nearly a hundred thousand a day. And, consumed data may be replayed in the future if required. So, after carefully considering several messaging queues we finally decided to continue with Apache Kafka.
  • Every setting is configurable.
  • Work seamlessly during high data load.
  • Partition mechanism.
  • Easy configurable.
  • Zookeeper configuration.
  • Front-end can be developed to configure properties.
  • UI for administrative configuration.
  • Partitioning.
  • Message retention configuration.
  • Integration with schema registry - Avro.
  • Opensource support.
  • Zero-down time.
  • Wide community support.
  • Steep learning curve.

Do you think Apache Kafka delivers good value for the price?


Are you happy with Apache Kafka's feature set?


Did Apache Kafka live up to sales and marketing promises?


Did implementation of Apache Kafka go as expected?


Would you buy Apache Kafka again?


Kafka can be used as a database but it is not recommended to store data for a long time. Also, if your application has a high data load then only we should utilize Kafka otherwise any other messaging queue is recommended. In addition, Apache Kafka provides far more features than just a simple messaging queue. Using Apache Kafka we can develop loosely coupled, real-time processing, and fault-tolerance architecture.

Evaluating Apache Kafka and Competitors

  • Product Features
  • Product Usability
  • Product Reputation
  • Prior Experience with the Product
Again, I would prefer to work with Apache Kafka.

Using Apache Kafka

Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file.
Like to use
Relatively simple
Well integrated
Feel confident using
  • topic creation
  • messages to produce and consume
  • maintain Kafka server
  • partitioning
  • message validation
  • adding security