Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
The Confluent platform is leading the charge in real time data streaming!
What do you like best about the product?
Confluent Kafka is a fantastic open-source streaming software that lets you build event-driven systems and allows backend systems to communicate with one another. The best thing about Confluent as a platform is that a large community uses it and its support system is like no other. They have excellent documentation on all their products, so all the information you need is available at the tip of your fingers.
What do you dislike about the product?
Some downside to the Confluent platform is that some of its products, like Confluent Kafka can be difficult to understand and visualize. However, there are tons of user-created tutorials that are available, and they are fantastic.
What problems is the product solving and how is that benefiting you?
Confluent Kafka specifically is helping me connect backend services by taking advantage of their event-driven consumers and producers, and from my experience, they do it better than their competitors at AWS or Apache.
- Leave a Comment |
- Mark review as helpful
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.
Confulent review in nanobebe
What do you like best about the product?
Easy to use and navigate, UI looks good and works well, can't see Avro messages
What do you dislike about the product?
a bit hard to get logs and good observability. I Think confluent should notify users when outage notify users via emails when they happen
What problems is the product solving and how is that benefiting you?
IOT Telemetry Bulk inserts, easy to use and no maintece requried
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.
Kafka if very hard to manage and professional help in this area is pretty week
What do you like best about the product?
Some of the visualization tools provided by the Confluent are very helpful
What do you dislike about the product?
Troubleshooting is very hard, the management is very expensive
What problems is the product solving and how is that benefiting you?
metrics gathering form various sources
Good managed Kafka Cluster, a bit expensive however for connect and ksqldb
What do you like best about the product?
Managed Kafka cluster, confluent API, Great documentation and community
What do you dislike about the product?
The cost is a bit prohibitive for the pay per use cluster since ksqldb creates so many internal topics (changelogs, repartitions) and the pricing for managed ksqldb is very constraining, and UDFs are not supported.
What problems is the product solving and how is that benefiting you?
Event driven microservices, stream processing pipelines, redefining our architecture where Kafka is the single source of truth. Productivity is not yet there yet since there is a certain learning curve and paradigm shift for developers on our team not yet acquired.
Scalability Of Java/Spring/Kotlin Function In One GCP Browser Session Through Confluent In A Region
What do you like best about the product?
Its flexibility in populating 1 function
What do you dislike about the product?
Not compatible for each browser sessions
What problems is the product solving and how is that benefiting you?
Atomic Web Application
Reliable Cloud Kafka
What do you like best about the product?
We don't have to maintain our Kafka brokers.
What do you dislike about the product?
Pricing by partition & It would be great to be able to assign more granular permissions to users.
What problems is the product solving and how is that benefiting you?
Supporting our Event Driven Architecture.
Recommendations to others considering the product:
Consider your architecture requirements carefully - don't over-engineer. Use SaaS where appropriate for your organisation.
showing 51 - 60