Cloud Equivalents

Events, queues & pub/sub · AWS vs Google Cloud

Amazon SQS vs Pub/Sub / Cloud Tasks

Amazon SQS maps partly to Pub/Sub pull subscriptions for queue-style consumption, and to Cloud Tasks for dispatching individual tasks with rate limits and scheduled delivery.

Partial match Use it to: Decouple producers and consumers with a durable queue so work is buffered, retried, and processed at the consumer's pace.

Last verified: · Edit on GitHub · Report an error

Side-by-side comparison

Message queues: AWS vs Google Cloud side by side
AspectAmazon Web ServicesGoogle Cloud
ServiceAmazon SQSPub/Sub
Cloud Tasks
LifecycleGenerally availableGenerally available
Generally available
What it isFully managed message queues. Standard queues are at-least-once with near-unlimited throughput. FIFO queues give ordered, exactly-once processing per message group. Dead-letter queues are supported.Global asynchronous messaging service with topics and push or pull subscriptions, used for fan-out, queues, and streaming pipelines.
Managed task queues that dispatch work to HTTP or App Engine targets with rate limits, retries, and scheduled delivery.
Pricing modelPer million requests (64 KB chunks), with FIFO priced higher, plus a monthly free tier and data transfer.Pub/Sub bills for message throughput (publish and delivery), storage, and cross-zone or cross-region transfer. Cloud Tasks bills per billable operation (API call or push delivery attempt).
DocsAmazon SQS docsPub/Sub docs
Cloud Tasks docs
Pricing pageAmazon SQS pricingPub/Sub pricing
Cloud Tasks pricing

Key differences

  • Pub/Sub is a topic/subscription model; each subscription acts like its own queue.
  • Cloud Tasks pushes tasks to HTTP targets rather than letting consumers poll.

Pricing summary

Pricing models only. No prices are quoted because they change by region and over time.

AWS
Per million requests (64 KB chunks), with FIFO priced higher, plus a monthly free tier and data transfer. Amazon SQS pricing →
GCP
Pub/Sub bills for message throughput (publish and delivery), storage, and cross-zone or cross-region transfer. Cloud Tasks bills per billable operation (API call or push delivery attempt). Pub/Sub pricing → Cloud Tasks pricing →

And on Azure?

Direct match Azure's equivalent is Azure Service Bus, Azure Queue Storage. AWS vs Azure comparison →

FAQ

What is the Google Cloud equivalent of Amazon SQS?

Amazon SQS maps partly to Pub/Sub pull subscriptions for queue-style consumption, and to Cloud Tasks for dispatching individual tasks with rate limits and scheduled delivery.

How does pricing compare between Amazon SQS and Pub/Sub and Cloud Tasks?

AWS: Per million requests (64 KB chunks), with FIFO priced higher, plus a monthly free tier and data transfer. Google Cloud: Pub/Sub bills for message throughput (publish and delivery), storage, and cross-zone or cross-region transfer. Cloud Tasks bills per billable operation (API call or push delivery attempt). Check the official pricing pages for current rates.

What is the Azure equivalent?

Azure Service Bus and Azure Queue Storage (direct match). Amazon SQS maps to Azure Service Bus queues (feature parity, including FIFO via sessions) or Azure Queue Storage (simple, cheap queues).

Related AWS vs GCP comparisons

Official sources