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?
Yes
Are you happy with Apache Kafka's feature set?
Yes
Did Apache Kafka live up to sales and marketing promises?
Yes
Did implementation of Apache Kafka go as expected?
Yes
Would you buy Apache Kafka again?
Yes
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
Pros | Cons |
---|---|
Like to use Relatively simple Well integrated Consistent Convenient Feel confident using | None |
- topic creation
- messages to produce and consume
- maintain Kafka server
- partitioning
- message validation
- adding security