Has enabled asynchronous communication and real-time data processing with strong performance
What is our primary use case?
We need to send a lot of asynchronous messages in this project, and we use the middleware and Apache Kafka on Confluent Cloud to guarantee asynchronous messaging between the services.
We use Apache Kafka on Confluent Cloud in the cloud.
We also use it with AWS.
What is most valuable?
The valuable features with Apache Kafka on Confluent Cloud are the messaging and the asynchronous messages; it's the basic, not advanced usage. It's only to create clusters to receive and send messages.
The point is the asynchronous messages and the scalability; it is important for us.
To guarantee the compliance of the architecture and the patterns for the company, to provide scalability, and to guarantee the security to send the messages.
The Kafka Streams API helps with real-time data transformations and aggregations.
It's very fast and helps us to create the project, guarantee the message delivery, and the performance. It's a good experience with very impressive processing and a very impressive project and product.
What needs improvement?
If it were easier to configure clusters and had more straightforward configuration, high-level API abstraction in the APIs could improve it. The clustering is a little hard for juniors and clients. It's suitable for senior engineers, but the configuration and clustering are very hard for juniors.
For how long have I used the solution?
I don't use Apache Kafka on Confluent Cloud more in this project these days. We are analyzing if we can use Apache Kafka on Confluent Cloud in another project next month, but today, we don't need this software.
What do I think about the stability of the solution?
I don't remember exactly the problem, but we did have a problem creating the cluster and scaling messages. After the correct configuration, we don't have more problems.
How are customer service and support?
I did have experience with AWS support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We did not use different streaming analytics before using Apache Kafka on Confluent Cloud.
We evaluated other options including WebSphere MQ and AMQP, and there was another solution I don't remember.
What about the implementation team?
We didn't use support from the companies. We used AWS support, and for the internal team, the infrastructure team has some knowledge about Apache Kafka on Confluent Cloud, but we never contracted a third-party company to support this project.
What other advice do I have?
Synchronized messages were very important for us.
We track performance and throughput as key metrics to evaluate Apache Kafka on Confluent Cloud's handling of event streams.
The benefits include improving the number of new customers that you can attain, having a more modular system, new functionalities, and high availability.
The main differences between WebSphere and Apache Kafka on Confluent Cloud are performance, throughput, and the knowledge from the developers in Brazil.
I have many people working with Apache Kafka on Confluent Cloud in Brazil, and I can send you their contact information if you send me an email.
I rate Apache Kafka on Confluent Cloud 10 out of 10.
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)
Experience with Confluent in my undergraduate research
What do you like best about the product?
Confluent has great documentation and developer advocacy resources. I learned Kafka and Kafka Streams almost exclusively using Confluent resources.
What do you dislike about the product?
I did not use Confluent tooling deeply or long enough to find downsides.
What problems is the product solving and how is that benefiting you?
Not a business problem, but helped me implement an event-stream processor using Kafka Streams. The streaming portion of the work was abstracted so I could focus on the algorithmic gist of my project.
"A Game-Changer for Real-Time Data Management"
What do you like best about the product?
With Kafka topics, it is possible to easily set up a pub/sub pattern and provide producers and consumers with complete end-to-end visibility using Confluent Center. Simple to scale through the addition of brokers and "no downtime" software update/patch deployments.
What do you dislike about the product?
Confluent has nothing that I don't like. Instead, they are focusing on improving the data flow from the CDC.
What problems is the product solving and how is that benefiting you?
Our architecture is being redefined using event-driven microservices and stream processing pipelines, with Kafka serving as the only source of truth. Since our team's developers still need to go through a specific learning curve and paradigm shift, productivity is still lacking.
Flexibility of use
What do you like best about the product?
Confluent made our event processing butter smooth. Millions of events fired and all got processed without breaking any sweat. Installation, configuration & integrations with relational database was cherry on top. As an administrator and developer, the documentation was so easy and relatable that we actually spend less time than we anticipated.
What do you dislike about the product?
Lack of third party learning resource and community support
What problems is the product solving and how is that benefiting you?
User attributions in performance marketing.
Amazing
What do you like best about the product?
The reliability and scalibility of the platform is really amazing,
The customer support is also very good.
The nhmber of features also are increasing.
What do you dislike about the product?
I don't dislike anything about confluent.
What problems is the product solving and how is that benefiting you?
Confluent makes analysis and big data management really simple and fast
Awesome
What do you like best about the product?
Nice sessions, to deliver best suggestions
What do you dislike about the product?
There is Nothing to dislike, A nice company with awesome team.
What problems is the product solving and how is that benefiting you?
It's benefits to keep Big data with ease to store and process.
Excellent documentation
What do you like best about the product?
Excellent documentation to understand difficult concepts. the concepts are written so clearly that it's very beginner friendly
What do you dislike about the product?
There could be more examples of real code for better understanding
What problems is the product solving and how is that benefiting you?
Producer consumer configuration
Plug it in and get started in minutes!
What do you like best about the product?
We are able to mobile projects literal in minutes and deploy the first app at a Client to run a poc in under 1 hr. The support is excellent, they help not only with the infra but also answer tech questions on Kafka.
What do you dislike about the product?
Features usually lag a bit when you use private networks, so this creates some problems at clients getting confused why they cannot use a feature they see in the marketing material.
What problems is the product solving and how is that benefiting you?
It removes the obstacles of adopting kafka at clients and provides support our clients require
Really afordable with great services
What do you like best about the product?
I used Confluent for data streaming for my website and it really gives easy and affordable prices for cloud storage.
What do you dislike about the product?
Managing multiple data stream can be little difficult.
What problems is the product solving and how is that benefiting you?
Confluent provides a lot of schema management and stream management service as well as it also simplifies connecting data sources to kafka.
Confluent makes running kafka clusters easy at scale
What do you like best about the product?
Confluent makes running Kafka clusters very easy all the things are taken care of as per demand (number of brokers to run, etc.)
ops team does not need to worry about the broker going down as it is automatically taken care of by confluent itself and traffic is routed accordingly
What do you dislike about the product?
The pricing model it a little confusing and configuring connectors is little bit of pain
What problems is the product solving and how is that benefiting you?
No need to self manage Kafka clusters once cluster is setup most of the things (availability, reliability) are taken care by confluent
