External reviews
118 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Not cheap, but good service, support and UI
What do you like best about the product?
The service has been stable and reliable thus far, and communication with sales and support teams has been good. Overall good documentation - a few things here and there have not been up to date or detailed, but in most cases it's clear and sufficient. The UI is easy to use and provides helpful information regarding application performance.
What do you dislike about the product?
We have run into the issue of some configuration options which would have been useful for us not being available in managed connectors. However, I must note that their sales and support teams have been helpful in communicating regarding this issue and proactive in suggesting alternatives and in opening feature requests. We have also had initial struggles setting up connectivity with our existing infrastructure in AWS.
What problems is the product solving and how is that benefiting you?
We have used Confluent Cloud thus far to replace an existing Elasticsearch indexing flow using commands by an event-driven approach using Kafka, which is more robust and performant. We are now moving on to other applications, also involving event stream processing.
Best managed kafka service for any scale
What do you like best about the product?
- Confluent cloud-managed Kafka service is the best in the industry. We have been using their managed Kafka service for more than 4 years now
- It abstracts the complexity of managing the Kafka clusters and helps us focus on building business applications rather than managing the infrastructure.
- It abstracts the complexity of managing the Kafka clusters and helps us focus on building business applications rather than managing the infrastructure.
What do you dislike about the product?
There are no downsides I can think of. If you are an enterprise customer and need a reliable Kafka infrastructure without the overhead of maintaining one yourself, confluent cloud is the go to solution.
What problems is the product solving and how is that benefiting you?
- Confluent kafka enables us to build real-time data applications without need of maintaining the kafka cluster ourselves.
- This is a huge time saver for application teams as they can focus on building their application than maintaining the cluster itself.
- Since it is managed service, it can be scaled up or scaled down easily
- It is able to handles millions of messages per minute without any performance issues
- This is a huge time saver for application teams as they can focus on building their application than maintaining the cluster itself.
- Since it is managed service, it can be scaled up or scaled down easily
- It is able to handles millions of messages per minute without any performance issues
So far so good
What do you like best about the product?
No need to self manage kafka clusters and kafka connect connectors.
What do you dislike about the product?
No option to whitelist IP addresses with access to kafka cluster
What problems is the product solving and how is that benefiting you?
A way to connect micro services with each other, message processing. Really useful that we can have multiple consumers processing same events.
Confluent Kafka has very much user friendly interface for viewing a topic's data and meta data.
What do you like best about the product?
GUI interface, SQL interaction, meta data showcase, topic information
What do you dislike about the product?
Not much i can think of, yet can be improved in the performance side
What problems is the product solving and how is that benefiting you?
I used the confluent Kafka product.
Yeah was useful
Yeah was useful
Confluent offers an easy to use interface for managing and operating Kafka Clusters.
What do you like best about the product?
The user interface provides a seamless experience and has lots of rich features and built-in tools to help you debug. I also like the Free tier clusters.
What do you dislike about the product?
The user interface can become laggy when dealing with lots of environments and clusters in the same tenant. It could be improved by providing a more resilient user interface that does not slow down when rendering large amounts of data.
What problems is the product solving and how is that benefiting you?
Confluent is solving our managed serverless problem. We do not want to self-manage our own infrastructure for hosting Kafka/serverless events. Instead, we use Confluent to focus on development instead of operations and maintenance.
Truly Serverless workloads with fully managed Kafka
What do you like best about the product?
Managing the Kafka and maintaining the underline infra is not an issue anymore, No more issues that are on our heads with proper Fault Tolerant Brokers and Kafka-Connect with Fully manged setup is really good.
What do you dislike about the product?
I did not find much of cons here, Its an amazing fully managed Service
What problems is the product solving and how is that benefiting you?
Less headaches with no more monitoring and no more additional human monitoring involved in managing the Kafka Cluster underline infra i.e Broker, and what fascinated me the most is the Fully Managed KafkaConnect with Confluent itself, with this our Event driven Architecture is much more simpler and very much error prone w.r.t to Operations.
Feature-rich cloud service with a wonderful support team
What do you like best about the product?
I should start off by clarifying that my company has not, at this time, moved forward with Confluent. That has to do with the direction our platform is taking, rather than the capabilities/quality of the Confluent solution. As we built a proof of concept with Confluent Cloud, it was very clear that it is feature-rich and very user-friendly. They are actively building a Terraform provider which will allow us to do even more IaC configuration, rather than manually or with deployment scripts.
All that said, I think the place where Confluent shined the most was with regards to the contacts with whom we worked throughout our process. They proactively reached out to us to provide helpful resources/articles/videos, and got on calls with us to discuss implementation solutions and to better understand our needs. There was no pressure for us to sign a contract or move forward with any sales process. Their goal was purely to make themselves available to us so we could build the best possible solution and follow best practices and design standards around the Kafka ecosystem.
Confluent Cloud also offers a lot of wonderful out-of-the-box connectors to systems like SQS, Lambda, etc. It saves you from writing a lot of boilerplate code.
All that said, I think the place where Confluent shined the most was with regards to the contacts with whom we worked throughout our process. They proactively reached out to us to provide helpful resources/articles/videos, and got on calls with us to discuss implementation solutions and to better understand our needs. There was no pressure for us to sign a contract or move forward with any sales process. Their goal was purely to make themselves available to us so we could build the best possible solution and follow best practices and design standards around the Kafka ecosystem.
Confluent Cloud also offers a lot of wonderful out-of-the-box connectors to systems like SQS, Lambda, etc. It saves you from writing a lot of boilerplate code.
What do you dislike about the product?
Honestly, this is a tough one to answer because my experience was so overwhelmingly positive. Though I've worked in eventually consistent and event-sourced systems before, I am a Kafka newbie. So, there is a pretty steep learning curve around it. While I do think that Confluent Cloud offered some great resources and tutorials, I wish they could go a step further with demonstrations of how to integrate Kafka with your software, with real-world examples of what the consuming/producing code might look like and how that would fit into your larger application.
Also, I was struggling to understand how multiple message producers could write messages with optimistic concurrency, a la EventStoreDb.
Also, I was struggling to understand how multiple message producers could write messages with optimistic concurrency, a la EventStoreDb.
What problems is the product solving and how is that benefiting you?
The problems we were looking to solve were to have an immutable ledger that serves as the source of truth for all changes to the system. I also want a system that leverages eventual consistency to help create loose coupling between services and to have a higher system resiliency/disaster recovery.
Some benefits I realized from Kafka/Confluent Cloud specifically are the power of KSQL, which essentially serves as an abstraction from a lot of the producer/consumer code you'd otherwise have to write in your application logic. It's incredibly powerful,and is drastically simpler to write than lambda/worker logic that you'd otherwise need to create.
Some benefits I realized from Kafka/Confluent Cloud specifically are the power of KSQL, which essentially serves as an abstraction from a lot of the producer/consumer code you'd otherwise have to write in your application logic. It's incredibly powerful,and is drastically simpler to write than lambda/worker logic that you'd otherwise need to create.
Recommendations to others considering the product:
Give it a shot. You can get an evaluation coupon code upon signup that allows you to play around with Confluent Cloud and try it for yourself.
Confluent is a great platform, easy and fast up with speed
What do you like best about the product?
Making your data available in a modern, flexible and easy scalable solution. I like all connectors avilable and security features now and coming.
What do you dislike about the product?
A guidance of how to get up and running with confluent as code.
What problems is the product solving and how is that benefiting you?
Integration between our applications on different platforms and also making AI run as near as possible in realtime. These integrations makes us more productive and we have also been able to benefit from our events several times in new use cases.
Recommendations to others considering the product:
Compare your internal knowledge in event programming, usage of connectors can be more costly and might need dedicated clustering. However if you have a single cloud environment it will be effective and easy to use. You will be up and running with your first cluster in no time.
But remember to do your homework with a good event architecture and document your events in schemas, it will give you lots of benefits in the long run.
I have used both opensource Apache Kafka and confluent cloud.
But remember to do your homework with a good event architecture and document your events in schemas, it will give you lots of benefits in the long run.
I have used both opensource Apache Kafka and confluent cloud.
Best Streaming Platform
What do you like best about the product?
Kafka topics store more data in comparison to Kinesis service provided by AWS. This gives more flexibility to handle large amount of data for our processing purposes.
What do you dislike about the product?
Managed service provides a better environment for our development and other purposes. It gives a plug and play feature to work with however when we talk about Kafka, we need to set up various things on our own which makes it a little complex in comparison to any managed service.
What problems is the product solving and how is that benefiting you?
We are using Kafka to have the near real time ingestion data pipeline. It allows us to move the data as and when the data arrives in the staging layer which we later pick up to create any KPIs or KRIs.
Overall best but few shortcomings
What do you like best about the product?
Compared to AWS kinesis, it does not have any message limits and highly customized and scalable streaming technology.
What do you dislike about the product?
It is lacking in terms of managed service and detailed information regarding the message delivery. There could be major enhancements in terms of enterprise support that we can use in AWS kinesis.
What problems is the product solving and how is that benefiting you?
We are using this software in a few of the POCs where we are streaming data from MS SQL server (operational data store) to Oracle server(for analytics) using pyspark and confluent kafka through hive tables. This is being done using Oracle CDC connector to implement DWH requirements.
showing 21 - 30