Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.
N/A
IBM Confluent
Score 9.1 out of 10
N/A
IBM Confluent Platform for Z and LinuxONE is an enterprise event streaming platform designed to run on Linux on IBM Z and LinuxONE environments. It enables organizations to create, manage, and process real-time data streams using Apache Kafka-based technologies. The platform provides capabilities for event ingestion, data integration, stream processing, schema management, connectors, and operational management. It supports deployment models including virtual machines, containers, and Kubernetes…
$0
Pricing
Google Cloud Pub/Sub
IBM Confluent
Editions & Modules
No answers on this topic
Basic
$0
Standard
Starting at ~$385
per month
Enterprise
Starting at ~$1,150
per month
Offerings
Pricing Offerings
Google Cloud Pub/Sub
IBM Confluent
Free Trial
No
No
Free/Freemium Version
No
Yes
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
Google Cloud Pub/Sub
IBM Confluent
Considered Both Products
Google Cloud Pub/Sub
Verified User
Anonymous
Chose Google Cloud Pub/Sub
Google Cloud Pub/Sub is a managed service compared to Apache Kafka.
Simple Queue Service (SQS) is an Amazon managed service that supports similar functionality as compared to Google Cloud Pub/Sub. However, we selected Google Cloud Pub/Sub as all other services in our platform …
Kafka looks like and ordered queue, there no deliver backoff, so if a message has a problem, it doesn't advance to the next one. Google Cloud Pub/Sub looks like more a SET of messages, and kafka like a LIST. In kafka a same message will repeat instantaneously while it is being …
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using …
Google Cloud Pub/Sub as a managed service is significantly more easy to use than a self managed Kafka cluster. As our software was already on GCP it was a no-brainer to use Pub/Sub due to the high level of integration and ease of use with other Google Cloud Platform services.
We considered several messaging platforms including Kafka and Kinesis but both would have required more developer work and didn't integrate as nicely with our ecosystem. RabbitMQ is another messaging platform I've researched and prototyped on; it also would have required more …
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 …
Using Google Cloud Pub/Sub will mainly depend on the cloud platform used. Our client didn't choose GCP for Google Cloud Pub/Sub, if we went with AWS we would be using SNS/SQS (obviously). However, Google Cloud Pub/Sub is a better solution in the GCP services compared to self-managed solutions such as RabbitMQ for instance (it is managed by GCP and integrates with GCP solutions).
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.
It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
It is easy to create Google Cloud Pub/Sub topics from both Web Console and CLI commands.
Google Cloud Pub/Sub supports creation of one or more subscriptions.
By supporting a BigQuery Pub/Sub subscription to automatically write to a BigQuery table it simplifies development by avoiding implementation of a custom micro service for writes to BigQuery.
They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.
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.
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.
You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
