Apache Kafka Review

Stable, free to use, and offers good stream processing


What is our primary use case?

Apache Kafka is used for stream processing, metric and log aggregations, and as a message queue for connecting different microservices.

What is most valuable?

The stream processing is a very valuable aspect of the solution for us.

What needs improvement?

Due to the fact that the solution is open source, it has a zookeeper dependency. If I could change anything about the solution, it would be that.

The solution could always add a few more features to enhance its usage.

For how long have I used the solution?

I've been with the company for at least one year, which is for how long I've been using the solution.

What do I think about the stability of the solution?

The stability of the solution is very good, even for large enterprise-level organizations. It's quite reliable. There aren't bugs or glitches that affect it. The solution doesn't crash.

What do I think about the scalability of the solution?

The solution is scalable, however, it's a 50/50 endeavor. It may require some management to build it out.

How are customer service and technical support?

The solution is open source, so there isn't technical support per se. The open-source community that surrounds the technology, however, is very good.

That said, our company provides technical support to our clients if they need it. It's 24/7 support and we try to reply within 20 minutes of receiving a request.

Which solution did I use previously and why did I switch?

Some of our clients are using Apache, while others are using other solutions. It depends on the company and its unique requirements.

How was the initial setup?

The difficulty or simplicity of the initial setup varies. It really depends on the organization and its requirements and infrastructure.

Deployment times vary. It can be up to a week in production, however, with some products online, some services can be deployed within minutes.

When you have already deployed the solution, and it's installed, it doesn't require very much maintenance. If it needs any, my company handles it for our clients. We have an entire team that can work on it.

What's my experience with pricing, setup cost, and licensing?

The solution is open source; it's free to use.

What other advice do I have?

What happens in our company is a little different. We basically provide services to other companies through Kafka, like our management services. It doesn't necessarily mean we're using the solution ourselves, however, we will be going and deploying Kafka for companies, like a systems integrator.

The version of the solution is normally 2.4, however, it depends on the requirements. Our cloud providers are always different due to the fact that the countries that we work with are all different. For example, in the US it could Amazon, Azure, or Google. It varies.

I'd advise other organizations considering using the solution to make sure they understand what the use case is. They need to know what their services will be and if they will be directed to Apache Kafka.

From a customer perspective, potential companies need to make sure they have an idea of how big it's going to be due to the fact that it's a cluster environment. It needs to be taken care of. Customers will need to know things like what is the message rate is which is coming into Kafka and how they will connect all those different microservices or any services together to Kafka.

From an infrastructure perspective, it's more of how big of a cluster a company needs. Who would be the producers to produce it, and who's the consumer who's consuming the data are a few questions that need to be asked.

I'd rate the solution eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Apache Kafka reviews from users
...who work at a Financial Services Firm
...who compared it with IBM MQ
Add a Comment
Guest