Why Snowflake architecture (storage, compute, services layers)? - Purpose & Use Cases

The Big Idea

What if your data system could work like a well-organized team, not a single overwhelmed worker?

The Scenario

Imagine you have a huge pile of data stored in different places, and you want to analyze it quickly. You try to do everything on one computer: storing data, running queries, and managing users all at once.

It's like trying to cook a big meal, clean the kitchen, and answer the phone all by yourself at the same time.

The Problem

This manual way is slow because the computer gets overwhelmed doing many jobs at once.

It's also risky: if one part breaks, everything stops working.

Plus, scaling up means buying bigger machines, which is expensive and complicated.

The Solution

Snowflake splits these jobs into three layers: storage, compute, and services.

Storage safely holds all your data in one place.

Compute runs your queries separately, so many users can work at once without slowing each other down.

Services handle tasks like security and metadata, keeping everything organized.

This separation makes the system fast, reliable, and easy to grow.

Before vs After

✗ Before

SELECT * FROM big_table WHERE date = '2023-01-01'; -- runs slow, blocks others

✓ After

USE WAREHOUSE warehouse1; SELECT * FROM big_table WHERE date = '2023-01-01'; -- runs fast, no blocking

What It Enables

It lets many people analyze huge data sets at the same time without waiting or crashing.

Real Life Example

A retail company can let marketing, sales, and finance teams run their own reports simultaneously without slowing down anyone else.

Key Takeaways

Manual all-in-one systems get slow and risky.

Snowflake's three layers separate storage, compute, and services.

This design makes data work fast, safe, and scalable.

Practice

1. Which layer in Snowflake architecture is responsible for storing data securely in the cloud?

easy

A. Network layer

B. Storage layer

C. Services layer

D. Compute layer

Solution

1. Step 1: Understand Snowflake layers

   Snowflake architecture has three main layers: storage, compute, and services.

2. Step 2: Identify the storage role

   The storage layer holds all the data safely in the cloud, separate from compute and services.

3. Final Answer:

   Storage layer -> Option B

4. Quick Check:

   Storage = Data storage [OK]

Hint: Storage layer always holds your data safely [OK]

Common Mistakes:

• Confusing compute with storage
• Thinking services store data
• Selecting network layer which doesn't exist in Snowflake

2. Which Snowflake layer runs queries and can scale independently?

easy

A. Compute layer

B. Services layer

C. Storage layer

D. Security layer

Solution

1. Step 1: Recall Snowflake layers

   Snowflake separates compute, storage, and services layers.

2. Step 2: Identify compute layer role

   The compute layer runs queries and can scale up or down independently from storage.

3. Final Answer:

   Compute layer -> Option A

4. Quick Check:

   Compute = Runs queries [OK]

Hint: Compute layer runs queries and scales [OK]

Common Mistakes:

• Choosing storage for query execution
• Confusing services with compute
• Selecting security layer which is not a main layer

3. Given Snowflake's architecture, what happens if you pause a compute warehouse?

medium

A. Data in storage is deleted

B. Services layer shuts down

C. Compute and storage both pause

D. Queries stop running but data remains intact

Solution

1. Step 1: Understand compute warehouse pause

   Pausing compute stops query processing but does not affect stored data.

2. Step 2: Analyze impact on storage and services

   Storage remains active and data is safe; services continue managing metadata and security.

3. Final Answer:

   Queries stop running but data remains intact -> Option D

4. Quick Check:

   Pause compute = stop queries, keep data [OK]

Hint: Pausing compute stops queries, storage stays safe [OK]

Common Mistakes:

• Thinking data is deleted on pause
• Assuming services layer stops
• Believing storage also pauses

4. A user reports slow query performance. Which Snowflake layer should you check first for scaling issues?

medium

A. Compute layer

B. Storage layer

C. Services layer

D. Network layer

Solution

1. Step 1: Identify cause of slow queries

   Slow queries usually relate to compute resources being insufficient.

2. Step 2: Check compute layer scaling

   Compute layer runs queries and can be scaled up or out to improve performance.

3. Final Answer:

   Compute layer -> Option A

4. Quick Check:

   Slow queries? Check compute scaling [OK]

Hint: Slow queries? Scale compute layer first [OK]

Common Mistakes:

• Checking storage for query speed
• Blaming services layer for performance
• Selecting network layer which is not part of Snowflake

5. How does Snowflake's services layer contribute to security and metadata management?

hard

A. It stores all user data and query results

B. It runs queries and manages compute resources

C. It manages authentication, metadata, and transaction coordination

D. It handles physical storage of data files

Solution

1. Step 1: Understand services layer role

   The services layer manages security, metadata, and coordinates transactions.

2. Step 2: Differentiate from storage and compute

   Storage holds data; compute runs queries; services handle control tasks like authentication and metadata.

3. Final Answer:

   It manages authentication, metadata, and transaction coordination -> Option C

4. Quick Check:

   Services = Security + metadata + coordination [OK]

Hint: Services layer controls security and metadata [OK]

Common Mistakes:

• Thinking services store data
• Confusing compute with services
• Assuming services run queries