G2

Verified User in Retail

Enterprise (> 1000 emp.)

3/28/2026

"A dependable way to connect services across GCP"

4.5/5

What do you like best about Google Cloud Pub/Sub?

What I like most is how flexible it is for event-driven workflows. We use Pub/Sub in a few different ways across our stack; for example, streaming error logs into a topic that triggers a Cloud Function to send Slack alerts, and also passing event data from Appsflyer to trigger Cloud Run services. It’s been very reliable and scales well without us having to think about infrastructure. Once topics and subscriptions are set up, it just works in the background. Review collected by and hosted on G2.com.

What do you dislike about Google Cloud Pub/Sub?

One downside is that it can be a bit hard to debug when something breaks in the pipeline. Since everything is asynchronous, you sometimes have to trace messages across multiple services (Pub/Sub, Cloud Functions, Cloud Run) to find the issue. Also, the UI isn’t the most intuitive when managing multiple topics and subscriptions. Review collected by and hosted on G2.com.

What problems is Google Cloud Pub/Sub solving and how is that benefiting you?

It’s helping us decouple different parts of our system and build event-driven workflows. For example, instead of tightly linking services, we can publish events (like logs, file changes, or external data such as AppsFlyer streams) and trigger downstream processing independently. This has made our system more scalable and resilient, and it allows us to react to events in real time; whether that’s sending alerts to Slack or triggering data processing jobs. Review collected by and hosted on G2.com.