Arkinu
AWS service comparison

Amazon RDS vs Amazon Redshift: differences and when to use each

Amazon RDS
Amazon Redshift

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Database

Amazon RDS

Managed relational database service with popular engines such as MySQL, PostgreSQL, MariaDB, Oracle Database, Microsoft SQL Server, and IBM Db2. AWS handles administration tasks such as backups, software patching, and failure detection and recovery.

Exam phrases that point here

  • «managed relational database with the least operational overhead»

    Amazon RDS handles provisioning, patching, backups, and failover for engines such as MySQL, PostgreSQL, MariaDB, Oracle, or SQL Server, without you managing the operating system.

    When not: If the scenario requires access to the operating system or an engine configuration that RDS does not allow, the option is to install the database on EC2. If it asks for high performance and storage replicated across 3 AZs with MySQL/PostgreSQL compatibility, also think of Amazon Aurora.

  • «high availability with automatic failover to another Availability Zone»

    A Multi-AZ deployment keeps a synchronous standby in another AZ and RDS automatically fails over to it if the primary or its zone fails.

    When not: Multi-AZ does not distribute reads: the standby of a Multi-AZ DB instance deployment does not serve traffic. If you also need to protect against the failure of an entire Region, you need a replica in another Region (or Aurora Global Database).

  • «offload read queries from the primary database»

    Read replicas receive an asynchronous copy of the changes and serve read-only queries, such as reports, to relieve the primary instance.

    When not: The replica can lag, so it does not work when a read must immediately see what was just written. And if the problem is that the same queries are repeated, a cache such as Amazon ElastiCache may be a better answer.

  • «copy of the database in another Region for disaster recovery»

    RDS lets you create read replicas in another Region; in a disaster, the replica is promoted to a standalone read/write instance.

    When not: Replication is asynchronous and promotion is manual, so the most recent writes can be lost. If the scenario asks for an RPO of seconds and fast recovery at global scale, it points more to Aurora Global Database; if restoring backups is enough, to copying snapshots or backups to another Region.

  • «many Lambda functions open too many database connections»

    RDS Proxy pools and reuses connections, so thousands of invocations do not exhaust the engine's connections; in addition, Lambda can authenticate with its IAM role.

    When not: If the application cannot tolerate the extra latency the proxy adds or has no connection problems, it connects directly. And if the bottleneck is reads, the solution is replicas or a cache, not a proxy.

Study Amazon RDS →

Analytics

Amazon Redshift

Fully managed, petabyte-scale data warehouse in the cloud. It lets you analyze large datasets with SQL and business intelligence tools, using provisioned clusters or Redshift Serverless.

Exam phrases that point here

  • «data warehouse for SQL analytics and business intelligence»

    Amazon Redshift is the AWS data warehouse: a massively parallel processing engine designed for complex analytical queries over large volumes of data and for feeding BI tools.

    When not: If the scenario describes application transactions (many small writes, OLTP), the answer is a database such as Amazon RDS or Amazon Aurora. If it is occasional queries over files in S3 without loading them, Amazon Athena is a better fit.

  • «query data lake data in S3 from the data warehouse without loading it»

    Redshift Spectrum reads the files in S3 where they are and lets you join them in the same query with tables loaded into Redshift.

    When not: If there is no Redshift warehouse and you only need one-off SQL queries over S3, Athena is simpler because there is nothing to provision.

  • «variable or intermittent analytics workloads without managing clusters»

    Redshift Serverless starts capacity when there are queries, scales on its own, and is billed by usage, without configuring or sizing a cluster.

    When not: If the workload is steady and predictable and you want fine-grained control of the configuration, a provisioned cluster may be the best option. Serverless doesn't turn Redshift into a transactional database either.

  • «analyze Aurora transactional data in near real time without building ETL processes»

    The zero-ETL integration replicates Amazon Aurora data into Redshift in a managed way and in near real time, with no pipelines to maintain.

    When not: If you only need to query the operational database from Redshift every now and then without replicating it, there are federated queries. If the destination is an S3 data lake, the path is usually AWS Glue or AWS DMS.

  • «share data from the warehouse between teams or clusters without copying it»

    Redshift data sharing gives access to live data from one warehouse to another (read and, if granted, also write access), which isolates workloads without duplicating data.

    When not: If the data is in an S3 data lake cataloged in Glue, sharing it across accounts with fine-grained permissions is the job of AWS Lake Formation.

  • «high availability of the data warehouse in the event of an Availability Zone outage»

    A Redshift Multi-AZ deployment keeps the warehouse in multiple zones behind a single endpoint and recovers in under a minute, with no data loss.

    When not: Cluster relocation is free but best effort and slower; if the scenario prioritizes cost over recovery time, it may be the answer. To recover from a Region outage, think of snapshot copies, not Multi-AZ.

Often paired with

  • Amazon S3
  • AWS Quick
Study Amazon Redshift →