Snowflake Architecture
Snowflake separates storage, compute, and coordination into three layers. See what each does, how warehouses buy concurrency, and what controls the credits.
-
-
Virtual Warehouse
A virtual warehouse is an independent Snowflake compute cluster. Size decides how fast one query runs; it is not the lever for many queries waiting at once.
-
Snowflake Credit
A Snowflake credit measures compute usage; the bill multiplies it by a price that varies by account and region. Storage and data transfer are billed otherwise.
-
Resource Monitor
A resource monitor watches warehouse credit use against a quota and can notify or suspend warehouses. It guards compute spend; it does not cap the whole bill.
-
Multi-Cluster Warehouse
A multi-cluster warehouse runs several identical clusters to reduce query queues caused by insufficient compute capacity. Each running cluster adds cost.
-
Micro-partition
Snowflake splits standard tables into small micro-partitions and records each column’s value range, so queries can skip data — if the values are grouped well.
-
Clustering Depth
Clustering depth measures how much micro-partitions overlap on a column. Lower means more data can be skipped — but query performance is still the real test.
-
Cloud Services Layer
The cloud services layer coordinates Snowflake — sign-in, metadata, query planning. It is billed only above 10% of daily warehouse use.
-
Secure Data Sharing
Secure Data Sharing grants other Snowflake accounts read-only access to live data without copying it — until the consumer is in another region.
-
Snowflake Architecture and Workload Design
Snowflake writes new files instead of editing old ones. See how that explains result reuse, the warehouse cache, Time Travel recovery, clones, and retention cost.
-
Time Travel
Learn how a warehouse keeps prior versions queryable for a retention window, what that recovers, and why longer retention shows up as storage cost.
-
Result Cache
Learn how a stored query result is reused, the exact conditions that allow it, and why timing a query twice measures the cache instead of the query.
-
Warehouse Workload Isolation and Concurrency
When dashboards wait behind an export, resizing may not help. Learn how compute separation, queues, workload classes, and access controls shape warehouse performance.