Professional Data EngineerBuilding and operationalizing data processing systemsHard
A data engineering team is building a real-time recommendation engine. They need to store user interaction data (clicks, views, purchases) that is constantly being updated and accessed with low latency. The data model is flexible and may evolve over time. The system needs to support high read and write throughput for millions of users globally, and strong consistency is not always required for every read. Which Google Cloud database service is most suitable?
- ABigQuery
- BCloud SQL
- CCloud Spanner
- DBigtable
Show answer & explanationAnswer & explanation
Correct answer: D. Bigtable
Bigtable is a highly scalable, low-latency NoSQL wide-column database ideal for large analytical and operational workloads, such as real-time recommendation engines that require high read/write throughput, flexible schema, and can tolerate eventual consistency for some reads.
Why the other options are wrong
- A. BigQuery is an analytical data warehouse, optimized for batch queries over large datasets, not low-latency, high-throughput operational reads and writes for individual user interactions.
- B. Cloud SQL is a relational database not designed for the extreme high read/write throughput and flexible schema required for this use case.
- C. Cloud Spanner offers strong consistency globally but is a relational database and might be overkill/too expensive for flexible-schema, high-throughput use cases where strong consistency isn't strictly needed for all reads.
Google Cloud Bigtable
A fully managed, scalable NoSQL wide-column database service for large analytical and operational workloads, offering low-latency reads and writes at high throughput.
- Petabyte-scale, high throughput (millions of ops/sec)
- Low-latency reads and writes
- Flexible schema (wide-column store)
- Ideal for time-series, IoT, and operational analytics
Memory trick: Bigtable: Massive scale, blazing fast.