Skip to content
tezvyn:

Data Storage Tiering: Pay Only for the Access You Need

Source: learn.microsoft.comMediumHow cards are made

Data Storage Tiering: Pay Only for the Access You Need

Treat data like items in a house: hot, frequently used data on the counter; cool, less-used data in the pantry. Cloud providers use this to price storage, letting you move old logs to cheaper tiers.

Why it exists

Cloud data grows exponentially, and storing all of it in high-performance, instantly-accessible storage is prohibitively expensive. Tiering was created to balance storage cost against access speed and frequency, allowing you to pay only for the performance you actually use for a given piece of data.

The mental model

Think of storage tiers like moving boxes. The things you need daily are out on your desk (Hot tier). Things you need this month are in a closet (Cool tier). Things you might need this year are in the attic (Cold tier). And things you must keep but almost never need, like old tax records, are in an off-site storage unit (Archive tier). You pay less for the less convenient locations.

How it works

Cloud providers offer several storage classes with different pricing and performance characteristics. A "Hot" tier has high storage costs but low access costs, optimized for frequent reads and writes. A "Cool" or "Cold" tier has lower storage costs but higher per-access fees, intended for data touched infrequently. An "Archive" tier offers the lowest storage cost but is offline; retrieving data can take hours and has the highest access cost. You, or an automated lifecycle policy, move data objects between these tiers as their access patterns change.

When to use it

Use tiering for any large dataset where access patterns change predictably over time. Three common places this shows up: first, application logs that are frequently queried for a week then rarely touched; second, backups and disaster recovery data that ages out; third, large datasets for ML training that are processed and then stored for compliance or future use.

When not to use it

Avoid aggressive tiering for data with unpredictable access patterns, as retrieval costs from cooler tiers can quickly erase any storage savings. It's also overkill for small datasets where the management overhead outweighs the cost benefit. If data needs consistent, low-latency access for its entire life, keep it in a hot tier.

One canonical example

A web application generates gigabytes of logs daily. For the first 30 days, these logs are in a Hot tier for real-time debugging. After 30 days, a policy moves them to a Cold tier for 90 days for occasional analysis. After that, they are moved to an Archive tier for long-term compliance. A key footgun: if you move a blob to the Cold tier (90-day minimum) and then delete it after 60 days, the provider will charge you an "early deletion" penalty equivalent to the 30 days of storage you skipped.

Interview question

For data with highly unpredictable access patterns, which storage strategy is generally recommended?

  • a.Implement an aggressive lifecycle policy to move it between Cool and Hot tiers.
  • b.Utilize a Cold tier, accepting higher access costs for lower storage fees.
  • c.Keep the data in a Hot tier to ensure consistent, low-latency access.Correct
  • d.Store it in an Archive tier to achieve the lowest possible cost.
Why?

Option C is correct because the card states to 'Avoid aggressive tiering for data with unpredictable access patterns' and to 'keep it in a hot tier' if data needs consistent, low-latency access. Option B is a tempting distractor, but the card warns that 'retrieval costs from cooler tiers can quickly erase any storage savings' for unpredictable access.

Just read this? Test yourself on what you have been reading.

Read the original → learn.microsoft.com

You just looked this up. Could you explain it out loud?

That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.

The iPhone app is on the way

We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.

Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.

Get it on Google PlayiPhone app coming soon

We are hiring for this. Open roles that interview on storage — each one lists the topics its interview covers.

See open roles