Google Cloud Pub/Sub vs. TIBCO Rendezvous

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).

Incentivized

I would recommend TIBCO Rendezvous to a colleague for several reasons. One of most important could be to use it on different operating systems (i.e. Windows, Linux) and be able to create real-time communications. Another reason could be the easy message addressing: only those who subscribe to specific subject receive the messages.

Incentivized

• A hands-off approach to publishing messages and subscribing to topics.
• Easy to use APIs.
• Useful, simple UI on cloud console to send messages for debugging, etc.

Incentivized

• Faster broadcast data.
• Exchange data across multiple networks.
• It works without a central server.
• Messages filtered based on specific subject.

Incentivized

• It is limited to work with the same platform but with different datasets at the same time, you must request a prior security authentication.
• It can sometimes lead to unexpected charges, as Pub/Sub will automatically keep on retrying messages continuously, even if failures are due to permanent code-level issues.
• Message re-deliveries don't apply for ingested services like with Python based client. Push messages tried to be delivered immediately and if your service is busy dealing with some other task, it won't be done OR goes into a queue

Incentivized

• RV doesn't support centralized administration to manage the delivery of synchronous messages in run time without changing its configuration which was done in code base

Incentivized

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.

Not likely to renew or buy the license as they are using the TIBCO EMS as the primary mode of communication.

Incentivized

It has many libraries in many languages, google provides either good guides or they're AI generated code libraries that are easy to understand. It has very good observability too.

Attending an official TIBCO classroom training, where you can have an active participation with an expert teacher, you can find the answers to all yours needs. In any case, if you are not satisfied on your requests, the teacher takes the time to find the best solution.

I had the opportunity to attend one and I could learn all features I needed for my business: now I can say TIBCO Rendezvous is very usable.

Incentivized

I have never faced a single problem in 4 years.

It's very fast, can be even better if you use protobuf.

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.

Incentivized

I never needed support for TIBCO Rendezvous. I always used it without any issue and until now I don't remember some situations where it interrupted its 24/7 uptime.

Incentivized

• Easy to setup Publisher, Subscribers and Message Queue service
• More Reliable and Easy Scalable with Google Managed services
• Easily integrated with most of the data sources we typically use for Data Storage and Analysis
• 10k Topics is a good enough number to build and deliver the business use cases
• Asynchronous and fallback mechanisms are great to ensure parallel delivery of the messages

Incentivized

TIBCO EMS provides centralized server administration to manger the delivery of services in run time

Incentivized

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.

• Pub/Sub has helped avoid data loss improving our customer value prop.
• Pub/Sub has reduced development time that would otherwise be needed to build a highly scalable queue.

Incentivized

• Positive - RV supports faster delivery of messages to multiple subscribers (asynchronous communications)
• Negative - RV doesn't support centralized administration and guarantee delivery is more accurate like EMS Persistent delivery mode

Incentivized