Apache Kafka on Confluent Cloud Reviews

We had a legacy website collecting user data as they logged into the portal. We wanted to capture that information in Snowflake and store it in a mobile app. We used Apache Kafka on Confluent Cloud for real-time data streaming.

It is a single platform to publish any information on any given topic. In case of huge transactions on the web or mobile apps, it helps you capture real-time data and analyze it.

There could be an in-built feature for data analysis.

We have been using Apache Kafka on Confluent Cloud for a year.

I rate the product’s stability a nine out of ten. There is room for improvement as we need to put some effort into setting it up to develop use cases. 

The product is highly scalable.

The technical support services are good.

The initial setup requires effort to deploy in the cloud or local environments. Once the servers and other prerequisites are ready, it is simple. It took us one month to complete the process. However, the approximate deployment time depends on particular use cases.

We implemented the product in-house.

I recommend Apache Kafka on Confluent Cloud and rate it a ten out of ten.

Overall, I think it's a good experience. Apache Kafka can be quite complex and difficult to maintain on your own, so using Apache Kafka on Confluent Cloud makes it much easier to use it without worrying about setup and maintenance.

The solution is expensive. 

I have been using Apache Kafka on Confluent Cloud, the platform's main product, for about three months.

I haven't experienced any major stability problems or bugs.

The tool is scalable. I've found Apache Kafka on Confluent Cloud to be very scalable. We've been able to scale up the volume of data we're handling without any issues with performance.

Setting up a new cluster on Apache Kafka on Confluent Cloud is pretty easy. You can click a few options, and there's also integration with other tools to create the necessary resources. However, there are some caveats to be aware of. The type of networking setup you choose can impact your functionality and visibility in the platform. For example, if you have a public cluster, you'll see more metadata information in the console than a more restricted network deployment.

Regarding pricing, Apache Kafka on Confluent Cloud is not a cheap tool. The right use case would justify the cost. It might make sense if you have a high volume of data that you can leverage to generate value for the business. But if you don't have those requirements, there are likely cheaper solutions you could use instead.

I rate the solution an eight out of ten.