The online blob access tier where storing data costs the most but accessing it costs the least.
Also called tier.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Hot in context, with comparison tables and the common traps.
Terms in this definition
- Online management group
Workloads that may talk directly to or from the internet, or that need no virtual network at all, go in this management group. It is a sibling of Corp and Local beneath Landing zones.
- BLOB
Short for binary large object: raw binary data, like pictures, audio, video or documents, that only an application can make sense of. Azure keeps these files as blobs in Blob Storage.
- Access tier
Setting for block blobs in standard accounts (Hot, Cool, Cold or Archive). Cooler tiers cost less to store but more to access.
- WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- LEAST
Pass up to 254 expressions to this T-SQL function and it hands back whichever is smallest. Both Fabric Warehouse and SQL analytics endpoints support it.
Related terms
- Analytics tier
Hot data tier of Microsoft Sentinel supporting hunting, detections and every Sentinel feature; its analytics retention can be extended to as much as two years.
- Application Insights Profiler
Capability of Application Insights that records performance traces from a running app, revealing slow requests and hot paths in the code. User behaviour is not what it profiles.
- Archive tier
An offline blob access tier offering the cheapest storage, meant for data that is hardly ever read. Archived blobs must first be rehydrated to the Hot, Cool or Cold tier, which may take as long as 15 hours, before you can read or change them, and ZRS, GZRS and RA-GZRS accounts can't use this tier.
- Caching policy
Determines the period for which KQL database or table data is held on local SSD in the hot cache so that queries over it are quick. The period may not exceed retention, and you configure it from Manage > Data policies.
- Cool
Online blob tier that is cheaper than Hot to store data in but dearer to access.
- Lambda architecture
Splits big data processing in two: a speed layer (the hot path) analyses events as they arrive, while a batch layer (the cold path) processes everything accurately but slowly. A serving layer joins up both sets of results.
- NVMe
Flash Optimized Azure Managed Redis keeps keys and hot values in memory while moving colder values, roughly 80 percent of capacity, onto this high-speed flash storage.
- Rehydration
Making an archived blob readable again by moving it to the hot, cool or cold tier, either by changing its tier or copying it. At standard priority this may take as long as 15 hours.