Skip to content

Multi Clusters Architecture Patterns in Redshift Serverless for Complex Workloads

4 minute read
Content level: Intermediate
1

This article provides guidance on Designing optimal multi warehouse architecture patterns for managing diverse analytical workloads, from continuous data ingestion to unpredictable ad-hoc queries, using Redshift Serverless's automated scaling capabilities.

Redshift Serverless

Amazon Redshift Serverless is a cloud data warehouse service that eliminates infrastructure management while automatically handling capacity provisioning and scaling. It allows data professionals to quickly analyze data by simply loading and querying it, without worrying about the underlying setup. The service automatically adjusts resources based on workload demands, charges only for actual usage, and works seamlessly with existing analytics tools.

This makes it an ideal choice for organizations seeking hassle-free data warehousing with predictable pay-as-you-go pricing

Redshift Serverless Use cases

Amazon Redshift Serverless is best suited for organizations needing flexible data analytics without infrastructure management. Key use cases include variable workloads, rapid development projects, cost-efficient real time analytics , modern data applications, and enterprise requirements. It automatically adapts to varying workloads and multiple users while maintaining performance and cost-efficiency, making it suitable for organizations of any size

Workload management in Redshift Serverless

Amazon Redshift Serverless Workload Management (WLM) offers a truly hands-off experience, eliminating the complexity of traditional WLM configuration. Administrators no longer need to worry about setting up queues, defining memory allocation, or managing query priorities. Redshift Serverless automatically handles resource allocation making it ideal for organizations that want to focus on data analytics rather than infrastructure management.

This simplified approach reduces administrative overhead, prevents configuration mistakes, and ensures consistent performance without the need for constant monitoring and adjustment of WLM parameters.

Sample Reference Architecture for complex workload

Data Warehouse Mix workloads

When dealing with diverse workloads as shown above in your data warehouse, where each workload has unique resource requirements, consider implementing a multi-warehouse architecture with Redshift Serverless. This approach can help optimize both cost and performance by separating workloads into dedicated environments, ensuring efficient resource utilization and better workload management

Redshift Serverless Multi Warehouse Architecture option 1 (Isolate Read workload)

Consider a scenario where you have two distinct requirements:

  1. Continuous real-time data ingestion operations require 24/7 system availability, though with minimal computational resources. This ingestion process can be implemented through various methodologies like Zero-ETL, Redshift Streaming, Database Migration Service (DMS) or any other tools.
  2. Ad-hoc workloads with varying complexity and usage patterns

For this scenario, we recommend following architecture to achieve optimal performance while maintaining cost efficiency.

Read workload Isolation

Redshift Serverless Multi Warehouse Architecture option 2 (Isolate Write/Read Workload)

Consider a scenario where you have following distinct requirements:

  1. Continuous real-time data ingestion operations require 24/7 system availability, though with minimal computational resources.
  2. Nightly or Seasonal Complex Data Ingestion and transformation jobs
  3. Ad-hoc workloads with varying complexity and usage patterns

In this situation, the following architecture using Data Sharing writes and read would provide both cost efficiency and optimal performance

Isolate Write/Read workload

Redshift Serverless Multi Warehouse Architecture option 3 (For very High Concurrent workload)

High-concurrency read operations from BI tools and dashboards present unique challenges in maintaining consistent performance while managing costs effectively in data warehouse environments. A strategic architecture leveraging Network Load Balancer (NLB) with multiple warehouses provides an optimal solution by distributing read queries across multiple consumer compute resources, ensuring sustained performance during peak usage periods. This design not only enhances query response times and user experience but also offers the flexibility to scale resources based on actual demand patterns, creating an efficient balance between performance requirements and operational costs.

NLB and multiple consumer for High Concurrency

For more information and customer success stories, please visit the following blog posts

sun-king-uses-amazon-redshift-data-sharing-to-accelerate-data-analytics-and-improve-user-experience

achieve-peak-performance-and-boost-scalability-using-multiple-amazon-redshift-serverless-workgroups-and-network-load-balancer

how-fanduel-adopted-a-modern-amazon-redshift-architecture-to-serve-critical-business-workloads

configure-monitoring-limits-and-alarms-in-amazon-redshift-serverless-to-keep-costs-predictable

AWS
EXPERT

published a year ago1.3K views

1 Comment

Amazon Redshift Serverless The ideal choice Organization data warehousing with predictable pay-as-you-go pricing https://amzn.to/4otAi6x Flexibility for resources actual demand pattern An efficient balance between performance requirement and operation coasts workflow management

replied a year ago