This website uses cookies to ensure you get the best experience.
Learn more.
Ridgefield operates a large sensor fleet. It needs low-latency key-based reads and writes over time-series data, with no relational joins. Which data-store choice and design are most suitable?
Published
- A single relational VM enlarged indefinitely without access-pattern analysis.
- Cloud Storage Archive with one object per individual database operation.
- Bigtable with row keys designed for balanced writes and required reads.
- BigQuery used for every synchronous per-sensor update.
Comments — 0
Sign in to comment