Professional Cloud ArchitectManage implementationEasy
A manufacturing company is deploying a new IoT solution on Google Cloud to monitor its factory equipment. Thousands of devices will send telemetry data continuously. This data needs to be ingested, processed in real-time for anomaly detection, and then stored for historical analysis. The company requires a highly scalable, low-latency messaging service to handle the ingestion of this high-volume, real-time data stream from IoT devices before it is processed. Which Google Cloud service is best suited for this initial data ingestion and messaging layer?
- ACloud Pub/Sub
- BCloud Storage
- CCloud Spanner
- DCloud SQL
Show answer & explanationAnswer & explanation
Correct answer: A. Cloud Pub/Sub
Cloud Pub/Sub is a fully managed, real-time messaging service designed for ingesting and delivering high volumes of events from various sources, making it ideal for the initial ingestion and messaging layer for IoT telemetry data.
Why the other options are wrong
- B. Cloud Storage is object storage, suitable for storing large files and historical data, but not designed for real-time, low-latency message ingestion from streams.
- C. Cloud Spanner is a globally distributed relational database, not a messaging service for high-volume event ingestion.
- D. Cloud SQL is a regional relational database service, not suitable for high-volume, real-time stream ingestion and messaging.
Cloud Pub/Sub
A fully managed, real-time messaging service that enables asynchronous communication between independent applications and services.
- Highly scalable and durable for message ingestion.
- Decouples publishers from subscribers.
- Supports both pull and push delivery models.
- Ideal for streaming analytics, IoT data ingestion, and event-driven architectures.
Memory trick: Pub/Sub pushes IoT data fast.