Google Cloud Pub/Sub vs. TIBCO ActiveMatrix Service Grid

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

It fits perfectly for SOA and EAI architecture with large numbers of services that required to be wired to each other, the binding virtualization is quite good to simply this part. For the simple scenario of orchestration and /or ESB architecture could be a better use traditional stack.

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

• reduce the number of http port required by services
• simplified the binding connection amongst services
• high scalability and fast deployment of applications

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

• health check of services and application features has been released with a lot of bugs that have never been fixed
• it is not so simple to apply the security policy to service/reference binding

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.

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

• 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 service grid has been chosen as a natural selection of the TIBCO product evolution. The high flexibility and the binding virtualization fits very well with client needs for its EAI applications due to the huge number of services and applications, the management of application dependencies during deployment, the advantage of perfect integration with EMS for logging

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

• The integration of old BW with BWSE and its interface quite similar to design time has reduced the cost of training for developers
• The TIBCO support for this product is no the best and clients complains too much about this. This required to find a workaround or force the client to move to new/or different product. Huge impact on ROI

Incentivized