Skip to content

How Snowflake's layered architecture separates storage, compute, and services

Snowflake uses a unique multi-cluster shared data architecture that combines elements of shared-disk and shared-nothing architectures. It consists of three independently scalable layers: database storage, query processing (virtual warehouses), and cloud services. This design allows storage and compute to scale independently, enabling elastic performance and concurrency.

1 · Learn the must-know

  • The storage layer holds all data in compressed, columnar, micro-partitioned format in cloud storage (S3, Azure Blob, or GCS), fully managed and optimized by Snowflake.
  • The compute layer consists of virtual warehouses (MPP clusters) that independently process queries; multiple warehouses can access the same data simultaneously without contention.
  • The cloud services layer handles authentication, metadata management, query parsing/optimization, security, and infrastructure management, coordinating across the entire system.
  • Virtual warehouses can be resized, suspended, resumed, or set to auto-suspend/auto-resume, and multi-cluster warehouses can scale out automatically to handle concurrency spikes.
  • Because compute and storage are separated, you only pay for storage used and compute time consumed, and scaling one does not require scaling the other.
  • Snowflake runs natively on AWS, Azure, and GCP, and its architecture allows for seamless cross-cloud and cross-region features like replication without changing the underlying data model.

2 · Check your understanding

Check this objectiveFree · always available

A Snowflake Practitioner manages a shared table where the ETL team loads data using WH_LOAD and the BI team runs dashboard queries using WH_BI. During month end, ETL loads on WH_LOAD slow down whenever BI users issue large scans on WH_BI. The requirement is that neither team's workload should compete for the same compute resources, and the table data must not be duplicated across teams. Which architectural principle allows this separation?

Your objective map0 tried · 0 answered correctly · 19 untouched

What you have tried across SnowPro Core's objectives, not a readiness score.

Snowflake AI Data Cloud Features and Architecture31% of the exam0 of 6 tried
Account Management and Data Governance20% of the exam0 of 3 tried
Data Loading, Unloading, and Connectivity18% of the exam0 of 3 tried
Performance Optimization, Querying, and Transformation21% of the exam0 of 4 tried
Data Collaboration10% of the exam0 of 3 tried

3 · Keep going