Google Cloud Pub/Sub vs. TIBCO Messaging

If you want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.

If you need a robust, extensible, reliable Enterprise Service Bus, with "Enterprise" being the key word here, TIBCO [Enterprise Message Service] will be able to fulfill every expectation. As proof of concept, or ad-hoc implementations, it might not be as well suited due to the infrastructure required.

Incentivized

• With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime.
• It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sources
• A simple and easy to use UI on cloud console for setup and debugging
• It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability

Incentivized

• Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
• Tibco EMS scales well, and this is another of our stringent requirements.
• Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.

Incentivized

• Would be nice if the queue could be extended beyond 7 days.
• We found it a bit tricky replay unacknowledged messages when needed.

Incentivized

• In terms of TIBCO Messaging, it would nice to have a more out-of-the-box way of linking its objects (queues, topics) directly to those of other popular solutions like MQ or Kafka.
• Not being able to filter (that is, using selectors) through patterns/subtexts on the message body is missed on occasions.
• Given the current trends and state-of-art, lift & shift of on-premise EMS clusters to cloud architectures should be more directly attainable.

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.

EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.

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.

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

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 GCP only for Pub/Sub the choice depends on other variables.

Incentivized

We also use other messaging products: IBM MQ, especially for integration with other systems (server2server), which has been an industry standard for a long time, and Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable.

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.

• Increased Efficiency with reliable and Google managed services up all the time wit Disaster Recovery in place as well
• Definitely Lower costs being a cloud based solution and easier to setup
• Faster Project delivery and go to market plan for the business use cases basis this technology at the back end

Incentivized

• Improved developer productivity as TIBCO Enterprise Message Service requires minimal coding
• Quicker time to market as the configuration / onboarding can be automated with this tool
• Ability to onboard more clients/consumers as the tool can handle large volumes seamless
• Improved visibility on the end to end process as the product provides monitoring by using JMS header information