SYSTEM Cited by 1 source

Google Pub/Sub

What it is

Google Cloud Pub/Sub is GCP's managed publish-subscribe messaging service — GCP's equivalent of managed Kafka-API services or AWS SNS + SQS. Clients publish messages to topics; Pub/Sub persists them and delivers them to subscriptions with at-least-once semantics (exactly-once as an opt-in). Used industry-wide as an event- ingestion and asynchronous-workload-decoupling layer on GCP.

Why it's on this wiki

One specific canonical appearance: the 2025-06-20 Redpanda retrospective on the 2025-06-12 GCP outage (sources/2025-06-20-redpanda-behind-the-scenes-redpanda-clouds-response-to-the-gcp-outage) names Pub/Sub as a customer-side data source feeding some Redpanda BYOC clusters, which meant that when Pub/Sub was degraded during the 2025-06-12 outage, those Redpanda customers' upstream ingestion was broken before Redpanda's availability became relevant. Redpanda frames this as asymmetric luck:

"For some of them, GCP's Pub/Sub served as the data source for their Redpanda BYOC clusters, so they needed to recover that first. While this meant Redpanda's operational status was less critical in those cases, it was still one less element for them to worry about."

The anecdote canonicalises Pub/Sub as canonical-upstream- source-for-streaming-brokers in the GCP ecosystem — a data- flow topology where a managed Pub/Sub layer absorbs high-cardinality event traffic and a broker (Kafka, Redpanda BYOC) behind it provides stream-processing / replay / re-consumption semantics.

Seen in

• sources/2025-06-20-redpanda-behind-the-scenes-redpanda-clouds-response-to-the-gcp-outage — Canonical wiki disclosure of Pub/Sub as a customer-side data source for Redpanda BYOC clusters on GCP, and of Pub/Sub as one of the GCP services degraded during the 2025-06-12 global outage. No mechanism depth on Pub/Sub's internal failure modes; Redpanda's vantage is that its customers' Pub/Sub → Redpanda ingestion pipelines broke at the Pub/Sub layer.

Related

• systems/gcp — the parent cloud platform.
• systems/kafka · systems/redpanda — peer streaming primitives that Pub/Sub is frequently upstream of in hybrid architectures.
• systems/redpanda-byoc — Redpanda's GCP customer deployments that ingest from Pub/Sub.
• systems/google-cloud-storage · systems/cloud-spanner — other GCP services in the same customer stack.