GCP - Cloud Firestore and Bigtable
You want to design a Bigtable schema for IoT sensor data that arrives every second from thousands of devices. Which approach best supports efficient queries for recent data per device?
You want to design a Bigtable schema for IoT sensor data that arrives every second from thousands of devices. Which approach best supports efficient queries for recent data per device?
hard📝 Best Practice Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Consider query pattern for recent data per device
Queries often request recent data, so sorting recent timestamps first helps.Step 2: Use reversed timestamp in row key
Reversing timestamp (e.g., max - timestamp) sorts recent data at the top for fast access.Step 3: Group by deviceID first
This groups data by device, making queries per device efficient.Final Answer:
Use row keys as deviceID#reversed-timestamp to keep recent data first and group by device. -> Option AQuick Check:
Reversed timestamp + deviceID = fast recent queries [OK]
Quick Trick: Reverse timestamp in key for recent-first order [OK]
Common Mistakes:
- Using timestamp first causes hotspots
- Storing all data in one row causes size limits
- Random UUID keys prevent efficient range scans
Master "Cloud Firestore and Bigtable" in GCP
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore GCP Quizzes