← Library / Lakehouse & Databricks
Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10
1 / 10

Use the arrows, swipe, or press ← → to move through the slides.

Lakehouse & DatabricksCarousel · 10 slidesSystem Design Series · Day 11

Hot / Warm / Cold Tiering — lifecycle policies and cost vs latency

Moving data to cheaper storage as it ages — tier classes on S3, GCS and Azure, lifecycle rules, and the latency you trade for the savings.

The trade-off I'd flag

Tiering saves money only if retrieval is rare. Model access patterns before setting lifecycle rules, or the first audit query from cold storage will cost more than a year of hot storage.

← PreviousS3/GCS Partitioning Strategies — pruning and the small-file problem Next →Compaction — Z-Ordering, bin-packing and VACUUM