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.