"With the new Bigtable capability, developers can set an age-based tiering policy on a table, with a minimum age threshold of 30 days. The service automatically moves data between SSD and infrequent access tiers, without requiring manual exports of infrequently accessed data. Anton Gething, a senior product manager at Google, and Derek Lee, a software engineer at Google, explain how tiered storage reduces operational overhead and eliminates manual data migration. They write:"
"Data is moved to the infrequent-access tier based on an age-based tiering policy, with an age threshold configured by the developer. When a cell's timestamp exceeds the configured age, it is moved from the SSD tier to the infrequent access tier. Data movement is based solely on the cell's timestamp and is unaffected by how often the data is read."
Google Cloud introduced Bigtable tiered storage preview to manage hot and cold data within a single Bigtable instance. Developers can configure an age-based tiering policy with a minimum 30-day threshold to automatically move cells from SSD to an infrequent-access tier based solely on cell timestamps. The feature integrates with Bigtable autoscaling and keeps data accessible through the same Bigtable API. Developers should use timestamp range filters in queries to target SSD-resident data and achieve optimal SSD performance. Common use cases include time-series data from sensors, equipment, and operations in industries like manufacturing and automotive.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]