Professional Data EngineerDesigning data processing systemsMedium
A global ride-sharing company processes millions of GPS coordinates per second from active vehicles. This real-time location data is critical for dynamic pricing, driver dispatch, and route optimization. The system requires ultra-low latency reads and writes (milliseconds) and must be highly scalable to accommodate fluctuating demand. The data schema is relatively simple (key-value pairs with timestamps). Which Google Cloud service is the most appropriate for storing and serving this operational data?
- ABigQuery
- BCloud Spanner
- CCloud SQL
- DCloud Bigtable
Show answer & explanationAnswer & explanation
Correct answer: D. Cloud Bigtable
Cloud Bigtable is a petabyte-scale, fully managed NoSQL wide-column database service, specifically optimized for high-throughput, low-latency reads and writes for large analytical and operational workloads. Its design makes it ideal for time-series data like GPS coordinates, where a simple key-value structure with timestamps and millisecond-level access is required.
Why the other options are wrong
- A. BigQuery is an analytical data warehouse, optimized for complex queries on large datasets, not for ultra-low latency operational reads/writes of individual records.
- B. Cloud Spanner offers global consistency and horizontal scalability for relational data, but its primary use case is for transactional data requiring strong consistency, and it may be overkill and more expensive for simple key-value time-series data compared to Bigtable.
- C. Cloud SQL is a relational database better suited for transactional workloads, not for millions of writes per second of time-series data at ultra-low latency.
Cloud Bigtable for Operational Time-Series
A highly scalable, low-latency NoSQL wide-column database on Google Cloud, optimized for large operational and analytical workloads, especially suitable for time-series data, IoT, and financial data.
- Petabyte-scale, fully managed NoSQL database.
- Ultra-low latency reads and writes (milliseconds).
- Ideal for high-throughput time-series data (IoT, sensor, GPS).
- Supports simple key-value lookups and wide-column structures.
Memory trick: For a 'Big Table' of fast-moving car data, you need a database that can write and read at lightning speed.