All Bridges/AWS to Azure Data Engineering Bridge/Data Warehousing & SQL Analytics
AWSAZURE Deep Dive
Data Warehousing & SQL Analytics

Amazon Redshift & Amazon Athena Azure Synapse Analytics

From Amazon Redshift & Athena to Azure Synapse MPP & Serverless T-SQL.

The 30-Second Mental Model Shift

In AWS, you choose between Amazon Redshift (MPP cluster) or Amazon Athena (serverless Presto over S3). In Azure Synapse, both capabilities live in the exact same workspace: Dedicated SQL Pools (MPP like Redshift) and Serverless SQL Pools (pay-per-TB lake queries like Athena).

1. Architectural Mechanism Comparison

AWS (What You Know)
Source

Amazon Redshift & Amazon Athena

Redshift provides provisioned/serverless MPP clusters with Slice distributions (KEY, ALL, EVEN). Athena provides serverless Presto/Trino queries over S3 ($5/TB).

Key Architecture Strengths:
  • Redshift Spectrum queries S3 data lakes directly from MPP clusters.
  • Athena provides instant $5/TB ad-hoc queries over S3 Parquet/ORC.
  • Redshift RA3 instances decouple storage and compute using managed storage.
AZURE (How It Works)
Mastery Target

Azure Synapse Analytics

Unifies both worlds in a single studio: Dedicated SQL Pools (60-distribution MPP matching Redshift) + Serverless SQL Pools (matching Athena $5/TB querying ADLS Gen2).

Why Azure Built It This Way:
  • Dedicated Pools use fixed 60 distributions (Hash, Replicated, Round-Robin) scaled with DWUs.
  • Serverless SQL (`OPENROWSET`) charges exact same $5/TB as Athena with zero cluster ops.
  • Integrated Apache Spark and Power BI Direct Lake.

2. Interactive Terminology & Concept Bridge

Interactive Concept Bridge: Terminology & Architectural Mapping

Click any concept below to see how your AWS knowledge directly maps into AZURE.

Mapping Deep Dive
Exact Concept Match
⚡ Direct cognitive shortcut
AWS (What You Know)

Amazon Athena ($5.00 / TB)

Serverless Presto/Trino querying S3 files.

AZURE (How It Works)

Synapse Serverless SQL Pool ($5.00 / TB)

Serverless T-SQL querying ADLS Gen2 via `OPENROWSET()`.

The Architectural Mental Shortcut:

Both bill on-demand at $5.00/TB scanned with $0.00 idle costs.

3. Visual Architecture Pipeline (Azure Synapse Analytics)

Azure Synapse 3-Stage Architecture: Data Lake ➔ Tri-Engine Compute ➔ Unified Lakehouse

Click any section below or run the simulation to explore Synapse Dedicated MPP vs. Serverless SQL.

1. Data Lake Ingress
2. Tri-Engine Compute
3. Lakehouse & BI
MPP Sharding
60 Distributions
Serverless Query
$5.00 / TB
DWU Scaling
DW100c - 30000c
BI Integration
Direct Lake Mode
The Query Engines
Stage Details

2. Tri-Engine Compute Architecture

Choose the exact engine for your workload: 1) Dedicated SQL Pools (60-distribution MPP with DWUs), 2) Serverless SQL Pools ($5/TB pay-per-query ad-hoc T-SQL), or 3) Synapse Spark Pools (managed Apache Spark).

Real-World Analogy

Like having a supercharged freight train (Dedicated MPP), an instant taxi (Serverless SQL), and a heavy crane (Spark) ready in the same yard.

Key Mechanics
  • Dedicated SQL Pool: Fixed 60 distributions (Hash, Replicated, Round-Robin) scaling from DW100c to DW30000c.
  • Serverless SQL Pool: Always-on `OPENROWSET()` T-SQL over data lake files ($0 idle cost).
  • Synapse Spark Pool: Auto-scaling in-memory data processing with shared Lake database metadata.
MPP Sharding
60 Distributions
Serverless Pricing
$5.00 / TB Scanned

4. Side-by-Side Code, CLI & Terraform Translator

Side-by-Side Code & Syntax Translator

AWS Syntax
-- Amazon Redshift DDL
CREATE TABLE fact_orders (
  order_id INT,
  customer_id INT,
  order_date DATE,
  amount DECIMAL(18,2)
)
DISTSTYLE KEY
DISTKEY(customer_id)
SORTKEY(order_date);
AZURE Equivalent
-- Azure Synapse Dedicated SQL DDL
CREATE TABLE [fact_orders] (
  [order_id] INT NOT NULL,
  [customer_id] INT NOT NULL,
  [order_date] DATE NOT NULL,
  [amount] DECIMAL(18,2) NOT NULL
)
WITH (
  DISTRIBUTION = HASH([customer_id]), -- Matches Redshift DISTKEY
  CLUSTERED COLUMNSTORE INDEX,
  PARTITION ([order_date] RANGE RIGHT FOR VALUES ('2026-01-01'))
);
Code Translation Notes:Redshift's DISTKEY(col) translates directly to Synapse's DISTRIBUTION = HASH(col).

5. Paradigm Shift Gotchas: Traps to Avoid in AZURE

Gotcha #1
medium

Synapse Fixed 60 Distributions

The Trap:

In Redshift, slices change based on node count; in Synapse, there are ALWAYS 60 distributions divided evenly among compute nodes.

How to Avoid It:

Ensure fact tables have enough rows (>2M) before hash distributing, otherwise use Round-Robin.

6. Test Your Mental Model

Quick Knowledge Check: Test Your AZURE Mental Model

Solidify your cross-cloud understanding with instant feedback.

1Which Redshift distribution style corresponds directly to Synapse's `DISTRIBUTION = REPLICATED`?