Storage class
A storage class is a selectable storage category or configuration that determines characteristics such as data access, performance, availability, retention, and cost.
Microsoft Azure in Action
A storage tier, or access tier, is a service configuration that determines how stored data is accessed, retained, and priced.
- How it is used
- Matches stored blobs and file shares to access needs while balancing performance and cost.
- How deep it goes
- Explains tier choices and pricing trade-offs, then shows file-share configuration without detailing every storage-account setting.
- Examples
- Uses customer orders, newsletter images, archived backups, and a half-filled Premium file share to illustrate choices.
- What you can do after
- Operate/configure it with a PowerShell file-share tier setting or blob life cycle rules.
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A storage class is a service-defined tier that determines the performance, availability, and pricing characteristics of stored data.
- How it is used
- Selects an AWS storage tier to match access frequency, latency, availability, retrieval urgency, and cost.
- How deep it goes
- Compares S3 and EFS classes with prices, latency, availability, retrieval behavior, and CLI restoration steps.
- Examples
- Uses S3 Glacier uploads, restoration commands, EFS pricing estimates, and latency comparisons.
- What you can do after
- Operate/configure S3 and EFS storage tiers while accounting for retrieval delays, access fees, latency, availability, and backup needs.
Architecting an Apache Iceberg Lakehouse
A storage access tier is a storage classification that associates data with an access pattern and corresponding cost and performance characteristics.
- How it is used
- Maps data access frequency and retention needs to storage cost and performance choices in cloud lakehouse architectures.
- How deep it goes
- Explains tier selection and lifecycle transitions with platform examples, but stops short of detailed pricing or policy configuration.
- Examples
- Uses Standard, Nearline, Coldline, Archive, Hot, and Cool tiers to illustrate active-to-historical data placement.
- What you can do after
- Configure storage classes and lifecycle transitions that align frequently accessed and historical data with cost and availability requirements.
Read how Architecting an Apache Iceberg Lakehouse explains storage class →
Related concepts
- cool access tierincludes · The Cool access tier is an Azure Storage access tier for infrequently accessed data, with lower storage costs and higher access costs and latency than the Hot tier.
- hot tierincludes · The hot tier is an Azure Files access tier with relatively lower storage cost and relatively higher transaction cost than the transaction optimized tier.
- AWS Glacierincludes · AWS Glacier is an Amazon S3 archival storage service or storage class for low-cost, infrequently accessed data with retrieval times ranging from minutes to hours.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.