Overall Satisfaction with Apache Kafka
We use Kafka as the queuing mechanism for records in an indexing pipeline. Previous to using Kafka we were working with tables in SQL Server to handle a queue in a situation that SQL is not really designed for. Kafka provides a simple and efficient system that does the job it was intended for, queuing and maintaining records in a queue, and works very well. We use Kafka for several processes in our organization that require records to be stored and be processed by dedicated servers.
- Queuing of records
- Easy expansion of Topic parititions
- An abundance of options for managing and maintaining queues
- Easy expansion of cluster for growth
- A management interface would be nice
- Built in logging tools
- Reporting the number of records in a Topic
- Providing offset information for all consumers in a given Topic
- The ability to make adjustments to Topics on the fly with minimal impact on processes.
- Kafka has made our indexing pipeline at least 3 times more efficient
- Records are accessible instantly when added to Kafka
- Having redundancy in the cluster has greatly helped with keeping indexing working with little effort on Operations teams.
We really needed to get away from using a SQL database to act as a queue for processing records, so a new solution was needed. Kafka is a leading software application initially designed for queuing messages which is essentially what we were looking for. It has a great user community and is used across the industry. We also use and trust several other products from Confluent which helped seal the decision.
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