Confluent Cloud is a cloud-native service for Apache Kafka used to connect and process data in real time with a fully managed data streaming platform. Confluent Platform is the self-managed version.
$0
IBM StreamSets
Score 8.2 out of 10
N/A
IBM® StreamSets enables users to create and manage smart streaming data pipelines through a graphical interface, facilitating data integration across hybrid and multicloud environments. IBM StreamSets can support millions of data pipelines for analytics, applications and hybrid integration.
N/A
Pricing
Confluent
IBM StreamSets
Editions & Modules
Basic
$0
Standard
Starting at ~$385
per month
Enterprise
Starting at ~$1,150
per month
No answers on this topic
Offerings
Pricing Offerings
Confluent
IBM StreamSets
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Confluent monthly bills are based upon resource consumption, i.e., you are only charged for the resources you use when you actually use them:
Stream: Kafka clusters are billed for eCKUs/CKUs ($/hour), networking ($/GB), and storage ($/GB-hour).
Connect: Use of connectors is billed based on throughput ($/GB) and a task base price ($/task/hour).
Process: Use of stream processing with Confluent Cloud for Apache Flink is calculated based on CFUs ($/minute).
Govern: Use of Stream Governance is billed based on environment ($/hour).
Confluent storage and throughput is calculated in binary gigabytes (GB), where 1 GB is 2^30 bytes. This unit of measurement is also known as a gibibyte (GiB). Please also note that all prices are stated in United States Dollars unless specifically stated otherwise.
All billing computations are conducted in Coordinated Universal Time (UTC).
—
More Pricing Information
Community Pulse
Confluent
IBM StreamSets
Considered Both Products
Confluent
Verified User
Anonymous
Chose Confluent
For our use case it was very important that the technology we were working with fit into our Azure architecture, and met our data processing size requirements to stream data within certain SLAs. Confluent more than met our performance requirements and compared to the others …
We chose to use the Confluent Platform because they provide enterprise-grade customer service support. Whenever we have trouble setting up or using the service, we can create a ticket for them and it will be resolved pretty fast. Kafka is the open-source software that comes …
First advantage is that this software is particularly new and it keeps updating according to the needs of the user. Other advantage is the it organises and produces conclusions on the basis of data without leaving any relevant information. Other softwares lack in data …
Before, we were using Informatica since most of our applications were running on on-prem servers. Later, when we started moving to the cloud, we tried Informatica Cloud, but it's more useful for batch-oriented than streaming. That's why one of our tech architects suggested IBM …
the IBM solution can be considered a good player in the specific perimeter of application because its main functionalities are working well, are easy to use, and complete. it allows also a good degree of freedom when it comes to personalization of pipelines and streams, and …
We chose IBM StreamSets because we used to own the product before selling it to IBM, so we have a tremendous amount of folks who are familiar with the product.
IBM StreamSets works well when compared to some of the other tools in the same category. They are easy to set up, development can be fast paced as the in-built / out of the box connectors that come along with the product.
StreamSets is a one-stop solution to design Data engineering Pipelines and doesn't require deep Programming knowledge, It's so user-friendly that anyone in Team can contribute to the Idea of pipeline design. In Hadoop One has to be programming proficient to use its various …
If your company needs to build event-driven applications, like in healthcare industry, you need to enhance interoperability, and you are seeking a reliable service with enterprise-grade support, Confluent is the best on the market you can get. Their product works great and they provide very good customer service.
Because real-world sources often change (new fields get added, formats get tweaked, etc.), StreamSets helps detect and adapt to those "schema drifts" or changes automatically, or with minimal manual intervention. That makes pipelines more resilient and significantly reduces the maintenance burden. Therefore, data sets with constantly changing sources/formats are great for StreamSets.
IBM Stream sets has been a wonderful addition to our technology stack. It has helped in some of our initiatives such as data engineering, data integration for not only external customers but also for internal purposes. The tool has also helped on our use cases related to streaming data. Moving to another tool would require significant amount of work and time.
because i think that overall the solution is having a positive impact on the business, it allows multiple benefits in simplification of the tasks and is capable of doing multiple process that are usually done by a combination of man and systems, reducing the time and effort required to have the data.
The support from the Confluent platform is great and satisfying. We have been working with Confluent for more than a year now. They sent out resident architects to help us set up Confluent cluster on our cloud and help us troubleshoot problems we have encountered. Overall, it has been a great experience working with the Confluent Platform.
Streamsets support has improved a lot in the last couple of years. We had some challenges in the beginning with support, but now the quality of the support and the responsiveness to tickets are better. We have contacted support multiple times when it came to scenarios where the system was slow or the output as not as we expected
For our use case it was very important that the technology we were working with fit into our Azure architecture, and met our data processing size requirements to stream data within certain SLAs. Confluent more than met our performance requirements and compared to the others scale options and cost to run it was more than financially viable as a platform solution to our global operations.
Before, we were using Informatica since most of our applications were running on on-prem servers. Later, when we started moving to the cloud, we tried Informatica Cloud, but it's more useful for batch-oriented than streaming. That's why one of our tech architects suggested IBM StreamSets for our real-time data streaming. During the POC stage, we were happy that the data streaming was way better with IBM StreamSets compared to the Informatica Cloud way of doing.