Building a Cloud Data Warehouse with Amazon Redshift - Choosing Between Serverless and RA3
Learn the criteria for choosing between Serverless and RA3 provisioned clusters, and how to prevent data silos using data sharing and Spectrum for data lake integration.
Redshift Architecture Overview
Redshift is a cloud data warehouse built on columnar storage and a massively parallel processing (MPP) architecture. Columnar storage reads only the columns needed for analytical queries, dramatically reducing I/O compared to row-oriented RDBMS systems. The leader node handles query parsing and execution plan generation, while compute nodes perform parallel data processing. RA3 instances separate compute from storage, with data stored in S3-based Redshift Managed Storage (RMS). Frequently accessed data is cached on local SSDs, so you don't need to worry about read latency from S3.
Choosing Between Serverless and Provisioned Clusters
Redshift Serverless automatically scales capacity in RPU (Redshift Processing Unit) increments, and you incur no cost when queries aren't running. It's ideal for intermittent workloads such as periodic BI dashboard queries, ad-hoc analysis, and development and test environments. Provisioned clusters (RA3), on the other hand, are suited for always-on workloads. In production environments where queries run continuously for 24 hours, combining provisioned clusters with Reserved Instances results in lower cost than Serverless. As a rule of thumb, Serverless has the advantage if daily query execution time is under 8 hours, and RA3 provisioned clusters have the advantage if it is at least 8 hours.
Data Sharing and Data Lake Integration with Spectrum
Data sharing is a feature that lets you share live data in real time between Redshift clusters. A producer cluster creates a data share, and a consumer cluster references it. No data copying occurs, and the consumer always sees the producer's latest data. This is effective when departments operate independent clusters but need to share common master data. Redshift Spectrum lets you run SQL queries directly on data stored in S3. Combined with columnar formats like Parquet or ORC, you can analyze petabyte-scale data lakes without loading data into Redshift. Using the Glue Data Catalog as a metadata store, both Redshift and Athena can query the same table definitions.
Redshift Pricing
Redshift Serverless is billed based on RPU (Redshift Processing Unit) usage, with a base RPU starting at 8 and costing approximately USD 0.375 per RPU-hour (as of August 2026). No charges apply when queries aren't running. For provisioned clusters, RA3.xlplus costs approximately USD 1.086 per node per hour (about USD 782/month), with Reserved Instance discounts of up to 64%. Redshift Managed Storage costs approximately USD 0.024 per GB per month. Serverless has the advantage for query execution of under 8 hours per day, and RA3 provisioned clusters have the advantage for always-on operation of at least 8 hours.
Table Design and Performance
Redshift performance depends heavily on table design. The key points are the distribution style, which decides how to spread data across the nodes, and the sort design, which decides the order in which to arrange data. If you distribute tables that you frequently join on the same key, data movement between nodes decreases and joins become faster. If you sort by the columns you frequently use for filtering, you can avoid reading unnecessary data. Automatic compression of data reduces both storage and the amount read. Designing distribution and sorting based on your query patterns is the key to a data warehouse that responds quickly even with large-scale data.
Loading and Transforming Data
The basic way to load data into Redshift is bulk loading from S3, and you can ingest data efficiently in parallel. If you take an ELT approach that performs transformations inside the data warehouse, you can process large volumes of data using its powerful processing capacity. If you turn frequently run aggregations into materialized views, which compute and hold the results in advance, you can speed up repeated queries. There is also a feature that automatically tunes table optimization, so you can reduce operational effort. Designing a flow that ingests raw data and shapes it within the warehouse into a form that is easy to analyze raises the efficiency of how you use data.
Concurrency and Workload Management
In environments where many users run queries at the same time, performance tends to drop as they compete for resources. Redshift has a mechanism that temporarily expands processing capacity when concurrency increases, so it can maintain responsiveness even at busy times. With workload management, you can route queries to queues by importance or type and control how resources are allocated. If you give priority to light queries that finish in a short time, you can keep them from waiting behind heavy queries. Allocating resources appropriately according to the characteristics of users and jobs leads to operations that use limited compute resources fairly and efficiently.
Security and Governance
Because important organizational data gathers in a data warehouse, protection and access management are indispensable. You encrypt data at rest and in transit, place the cluster in a VPC, and control the network. If you grant access permissions according to roles and restrict the visible scope at the column or row level, you can change what each user sees even in the same table. You can also protect sensitive columns by masking them. You record who accessed which data so that you can audit it. By applying consistent permission management when you integrate with a data lake as well, you can achieve well-controlled data governance across the whole organization.
Summary
Redshift is a cloud data warehouse that delivers high-speed analytics on petabyte-scale data. A phased approach of starting small with Serverless and migrating to provisioned clusters as workloads grow is effective. By leveraging data sharing and Spectrum, you can prevent data silos and achieve unified analytics across your data lake.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
- Amazon Redshift official page
- Amazon S3 official page
- AWS Glue official page
- AWS Documentation (official)
If this page and the official documentation disagree, treat the official documentation as authoritative.