No more typing reviews! Try our Samantha, our new voice AI agent.
AbhishekSingh11 - PeerSpot reviewer
Infrastructure Solutions Architect at a real estate/law firm with 10,001+ employees
Real User
Oct 29, 2022
Assists us in processing vast chunks of data in real-time
Pros and Cons
  • "The solution can handle a high volume of data because it works and scales well."
  • "To date, we have seen improvements in performance and scalability, so we recommend this solution."
  • "It could be improved by including a feature that automatically creates a new topic and puts failed messages."

What is our primary use case?

Our primary use case for this solution is processing vast chunks of data in real-time. We deploy the solution on cloud.

What is most valuable?

The processing is better, and the connectors feel better than other solutions we have used. Additionally, the solution can handle a high volume of data because it works and scales well.

What needs improvement?

This solution is different from other products we have used. It could be improved by including a feature that automatically creates a new topic and puts failed messages. When we moved to this solution, we noticed that failed messages do not automatically go into Dead Letter Queue (DLQ), which we had when we used Azure. We want something similar to be included in Confluent Kafka.

The Azure Service Bus background should be improved where the message processing and messages fail and automatically go into a DLQ. In Confluent Kafka, there is no concept of DLQ, so if any messages fail, you have to handle it on your end and push it to another topic. But in Azure Service Bus, it happens automatically if any message delivery fails. It puts it in a DLQ. We didn't bother about anything on the code front, but with Confluent Kafka, there is no concept of DLQ, and you have to manage when a message fails to deliver. We have to push it to another topic manually. This should have been on the Confluent Kafka, and if anything fails, it should automatically move the message to another topic that has been created. Still, we have to do this using our code explicitly.

For how long have I used the solution?

We have been using the solution for approximately six months.

Buyer's Guide
Confluent
November 2026
Learn what your peers think about Confluent. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
921,774 professionals have used our research since 2012.

What do I think about the stability of the solution?

The solution is stable. In our limited experience, we haven't found anything that would highlight that it's not stable.

How was the initial setup?

I wasn't part of the initial setup.

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

We need visibility on the licensing costs.

Which other solutions did I evaluate?

When evaluating the use case compared to the Service Bus architecture we previously used, the performance is better and more tolerant than a competitive system. Hence, because of our data volume, it can handle high-volume data, and its performance is better than other systems.

What other advice do I have?

I rate the solution nine out of ten. The solution is good, but it can be improved by including a feature that stores failed messages. I recommend this solution to new users because we went through different tech analyses and then adopted this solution. To date, we have seen improvements in performance and scalability, so we recommend this solution.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Human Resources Executive at Sticky IO
Real User
Aug 25, 2022
Wide range of features, reliable, and different levels of support available
Pros and Cons
  • "The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
  • "The pricing model should include the ability to pick features and be charged for them only."
  • "The pricing was high for our needs. We should not have to pay for features we do not use."

What is our primary use case?

We are using Confluent for the basic use cases of messaging. For example, creating a topic and posting the events on the topic.

What is most valuable?

The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category.

For how long have I used the solution?

I have used Confluent within the last 12 months.

What do I think about the stability of the solution?

Confluent is a stable solution.

What do I think about the scalability of the solution?

The scalability of Confluent is good.

We have four to five developers using the solution. Depending on our testing we might increase the usage of the solution.

How are customer service and support?

Confluent has different levels of support.

I rate the support from Confluent a four out of five.

How was the initial setup?

The initial setup of Confluent is straightforward.

What about the implementation team?

We used a third-party CICD platform to do the implementation of Confluent. The solution only requires one person for maintenance. 

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

The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use. 

The pricing model should include the ability to pick features and be charged for them only.

The price of the solution is based on the capability and input and output of topics received.

What other advice do I have?

We were trying to evaluate Confluent, MSK, and Kafka for our purpose. We did a POC for all three and since we had a classic use case, we went with MSK. Confluent has the widest range of features out of the three and Kafka requires more people for maintenance. We were not using all the features, which is why we went with MSK.

My advice to others is if you have extensive use cases of messaging, you should work with Confluent. However, if you only have a basic messaging use case in place, you can explore other options.

I rate Confluent a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Confluent
November 2026
Learn what your peers think about Confluent. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
921,774 professionals have used our research since 2012.
Consultant at a consultancy with 10,001+ employees
Real User
Nov 21, 2021
Scalable, flexible, open source solution
Pros and Cons
  • "The design of the product is extremely well built and it is highly configurable."
  • "It would be great if the knowledge based documents in the support portal could be available for public use as well."

What is our primary use case?

Our use cases include data streaming, enterprise architecture, integrations, and complete data saving needs, some AI workloads, and standardization. We work on all of these.

How has it helped my organization?

The biggest benefit is that it is open source. You have the flexibility of opting or not opting for enterprise support, even though the tool itself is open source. 

The second benefit is it's very modern and built on Java and Scala. You can extend the features very well, and it doesn't take a lot of effort to do so.

Then the performance and community support, which we get while we do any POT, proof of theory work. The community support we receive is also really good.

The knowledge base on the Confluent website is also a good benefit. 

What is most valuable?

In terms of the valuable features, first would be scalability, then open source. You can use it for POCs, and if you are going to production with this technology, then you can opt for platinum support. The design of the product is extremely well built and it is highly configurable.

Whether you have a custom use case or out-of-the-box implementation, you can configure it according to your needs. The tool is very flexible, so you can configure it according to your use case and it's easy to administer. Because it's open-source, you're transparent as well. Nothing is a black box when you are working with Confluent.

You can extract and look at the code of what's happening. You can customize the code also because it's open source. I find all these features very interesting and appealing.

What needs improvement?

It would be great if the knowledge based documents in the support portal could be available for public use as well. If Confluent would publish the knowledge base, best practices, proper documentation; that would be helpful for folks who do not have support lines or are just assessing whether they can fit Confluent into their use case.

For how long have I used the solution?

I have been working with Confluent for more than four years.

What do I think about the stability of the solution?

Confluent is a reliable product.

What do I think about the scalability of the solution?

I have been working on Confluent with two companies and around ten people. We use it on a daily basis. It's basically a vertical and it integrates all the sources.

How are customer service and support?

We use the solution on-premise with enterprise support. This is an open-source technology and the setup I was working on was on-premise. There are various features of the platinum enterprise support with Confluent.

We can go to them for knowledge modules and best practices. We can reach out to Confluent regarding any product which is currently active or if we identify a bug in any product. We reach out with a support request. I'm satisfied with the support.

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

While I was using Confluent, I worked on use cases involving other traditional message use and conventional streaming platforms. The Confluent platform actually outlines everything, so it's a great product in this field.

How was the initial setup?

The implementation is somewhere in between simple to moderate. It depends on the use cases, but it is not a very difficult tool to handle. If you have a team of IT professionals then it takes less time to scale to Confluent. The setup is rather simple and the architecture is microservices-based.

A team of three to five people would easily implement. Again, I'm talking about designing and a POC implementation. So whenever you move to production or scalability, you just have to replicate the configurations.

For a general mini architecture, you can deploy very easily with three to five people.

The timeframe to implement depends on the complexity of the use cases. Sometimes it takes a month or two; sometimes it can take a week or two. 

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

You have to pay additional for one or two features. The monitoring simple solution call conference control center and Confluent replica for disaster recovery. You have to pay for these two use components, but it is included in the support package.

What other advice do I have?

The solution requires a support team. A minimum of two people are required to administer and handle the support activities in the event of outage. So any service will need, so Confluent is not no different in that perspective.

The support is very good and it's open source. Companies can easily pre-assess whether it fits their needs. They can even do performance benchmarking. 

I would give the solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
it_user1582965 - PeerSpot reviewer
Project Management Officer at a computer software company with 501-1,000 employees
Vendor
May 23, 2021
Scalable, easy to use, and very stable
Pros and Cons
  • "A person with a good IT background and HTML will not have any trouble with Confluent."
  • "Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent."
  • "In Confluent, there could be a few more VPN options."
  • "The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include."

What is our primary use case?

We are using Confluent for documentation. We use it to have documentation for the Agile team, as a reference or to share it with the stakeholders. It holds the project data, and what's happening right now. 

At a higher level, the business initiative and all things related to tracking high-level, enterprise-level tasks is something we are not doing it right now. We are doing that part in a very traditional way using Excel sheets, which is very manual work. We haven't automated it yet. 

What is most valuable?

A person with a good IT background and HTML will not have any trouble with Confluent.

The solution is stable. 

The scalability is good.

The solution offers good dashboards for the team they are easy to navigate and you can install them on your desktop or the local machine.

What needs improvement?

The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include. In my earlier organization, people used to struggle in adding the HTML tags to the Confluent. However, if a person is from an IT background, and he or she knows how to add the tags and browse product documentation, for them it is easy. A new user must go through the few training sessions for Confluent.

In Confluent, there could be a few more VPN options. I remember in my previous company, I had an issue in adding a query where I could pull down information from Jira. The product, the team productivity, the team timesheets, et cetera. A few of those plugins must be more advanced in Confluent.

The plugin options need to be improved. I don't know whether we have something in Confluent where we can have a plugin for support teams. If not, that would be ideal.

For how long have I used the solution?

I've been using the solution for about six years or so.

What do I think about the stability of the solution?

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

The product can scale. However, the person must be used to that tool. It depends on how quickly the user can pick up working on that.

We likely have as many as 300 people using the solution.

I'm not sure if the organization intends to increase usage in the future.

How are customer service and technical support?

I don't directly deal with technical support. That's all handled by our backend team, and therefore I leave it to them. Without any direct experience, I can't speak to how knowledgeable or responsive they are. 

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

I've used other project management-related products and document repository kinds of products like SharePoint or Microsoft Project.

Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent. Confluent have many options compared to SharePoint.

How was the initial setup?

In terms of the installation, for us, we have an Agile admin person that handled the setup. I wasn't a part of the process. I can't directly speak to the experience. I remember creating the project, however, I did not do the deployment part. 

I'm not sure how many people you need to handle the deployment. It might be four or five individuals.

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

I don't directly handle the licensing. My license is given to me. Therefore, I don't know the terms of the licensing or the exact costs.

What other advice do I have?

We're customers and end-users.

The end products we have are Jira, Confluent, Bitbucket as well as Dynatrace. I'm not sure which plugins we use. Confluent we are using just for the documentation. 

I'd rate the solution at an eight out of ten. It's been very handy for me and the team.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1439427 - PeerSpot reviewer
Delivery Head IT & IS at a non-tech company with 10,001+ employees
Real User
Apr 18, 2021
Easy to set up, scalable, and competitively-priced product
Pros and Cons
  • "Their tech support is amazing; they are very good, both on and off-site."
  • "Confluent is an amazing tool that is highly configurable, integrates very well with Jira, and lets you create nice documentation for various products while also supporting reporting and online content hosting."
  • "It could have more themes. They should also have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira."
  • "It could have more themes. The themes in the version I'm using are very limited; they offer two to three themes."

What is our primary use case?

Confluent is an amazing tool. It gives you the ability to basically create nice documentation for various products. It is highly configurable and integrates very well with Jira. You can use it for reporting as well. When it comes to hosting online content, it is in competition with SharePoint.

What needs improvement?

It could have more themes. The themes in the version I'm using are very limited; they offer two to three themes. 

They should have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira.

For how long have I used the solution?

I have been using Confluent for 15 years. 

What do I think about the scalability of the solution?

Confluent is scalable. 

How are customer service and technical support?

Their tech support is amazing; they are very good, both on and off-site. Whenever we have a query for them, they got back to us in time and with the information that we needed. 

How was the initial setup?

I think the documentation that Atlassian provides has all the information you need to carry out the installation. The installation is very straightforward; I didn't come up against any challenges. 

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

I think Confluent's pricing is very competitive compared to other products on the market. This is especially considering its configurability and extensibility.

What other advice do I have?

I would recommend this product. 

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Download our free Confluent Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2026
Product Categories
Streaming Analytics
Buyer's Guide
Download our free Confluent Report and get advice and tips from experienced pros sharing their opinions.