TrustRadius: an HG Insights company

Google Cloud Pub/Sub Reviews & Insights

Score9 out of 10

24 Reviews and Ratings

Community insights

TrustRadius Insights for Google Cloud Pub/Sub are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Ease of Use and Scalability: Users have appreciated the ease of use and scalability offered by the data streaming service. They found it intuitive to navigate and were able to easily scale their operations as needed.

Valuable Dead Letter Queue Functionality: Some users have noted the integrated Dead Letter Queue functionality as a valuable feature that has helped them manage messages effectively and ensure robust message delivery.

User-Friendly Pub/Sub UI: Reviewers have praised the user-friendly Pub/Sub UI, especially its integration with BigQuery and Cloud Storage. The seamless interface has made it convenient for users to work across different platforms effortlessly.

Google Cloud Pub/Sub Reviews

3 Reviews
Engineering

Overview of Google Cloud Pub/Sub

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

Fully managed messaging middleware useful for service integration. We have mainly used it for large scale logs from Kubernetes clusters. Pub/Sub proved to be easy to use, with a clear, user-friendly UI, well documented SDK, built-in elasticity and was the foundation for a real time data management system. Overall, very pleased with Google Cloud Pub/Sub.

Pros

  • Messaging
  • Scalable
  • No-ops
  • Secure

Cons

  • Only usable within GCP

Likelihood to Recommend

Google Cloud Pub/Sub is ideal for any real-time data project, especially with large datasets in the terabytes per day range. We have used it successfully in a variety of use cases ranging from recommendations engines (where we’d need to ingest in real time people’s clickstream) to more ops related Kubernetes cluster provisioning and monitoring (based on Kubernetes control plane events).

Alternatives

Amazon Managed Streaming for Apache Kafka (Amazon MSK), Apache Kafka and Amazon Simple Notification Service (SNS)
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.
Vetted Review
Google Cloud Pub/Sub
5 years of experience

Reliable Pub/Sub Vendor

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

Google Cloud Pub/Sub is used for processing scheduled tasks, sending notifications to clients and other background job execution. It helps in the point-in-time queue to send notifications to customers. As a team lead, I helped my team to transition from the legacy queue system to the Google Cloud Pub/Sub real-time system to capture Play billing alerts in real time.

Pros

  • Queue Caching
  • Notification Service
  • Background Task

Cons

  • Priority Queue is a missing feature

Likelihood to Recommend

Every Google Play billing console user who handles subscriptions at scale should definitely adopt pub/sub for seamless processing.

Alternatives

Amazon Simple Queue Service (SQS)
Amazon SQS has no integration with google play billing whereas Google Cloud Pub/Sub had native integration with google cloud billing, Play billing.
Vetted Review
Google Cloud Pub/Sub
2 years of experience

Pub/Sub, simple + reliable + scalable = a great product

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

Our company currently uses Pub/Sub to reliably queue up messages that arrive rapidly from multiple instances. It's a very technical product and really only used by the development team rather than company-wide. The primary problem it addresses for us is its ability to handle scale and resilience in the case of errors.

Pros

  • Highly scalable.
  • Queues messages for up to 7 days if not acknowledged.

Cons

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

Likelihood to Recommend

Scenarios where GCP Pub/Sub is well suited:
- Companies processing large amounts of data where eventual consistency is acceptable and the ability to recover from loss desirable.
- Companies already working with other GCP products (it integrates well with other products in the ecosystem).

Scenarios where GCP Pub/Sub is less well suited:
- If you're not queuing a huge amount of data it's probably overkill.

Alternatives

RabbitMQ, Apache Kafka and Amazon Kinesis
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 developer time to implement as well but might be a good alternative for a hobbyist or a team looking for more customization.