Database
Amazon Aurora
Fully managed relational database engine compatible with MySQL and PostgreSQL that is part of Amazon RDS. It uses a distributed storage subsystem that grows automatically and automates database clustering and replication.
Exam phrases that point here
«MySQL- or PostgreSQL-compatible database with higher performance and availability»
Aurora is compatible with MySQL and PostgreSQL, so existing applications work with few or no changes, and its distributed storage replicates the data across three AZs.
When not: If the engine is Oracle, SQL Server, or Db2, Aurora does not apply (although Babelfish helps migrate from SQL Server to Aurora PostgreSQL); the answer is usually Amazon RDS. And if access is by key at massive scale with no need for relational SQL, Amazon DynamoDB is a better fit.
«failover in seconds with no data loss»
Aurora Replicas share the storage volume with the writer instance, so any of them can be promoted to primary without losing data, normally in 30 seconds or less.
When not: This covers the failure of an instance or an AZ within the Region. If you must survive the failure of an entire Region, the clue points to Aurora Global Database.
«up to 15 read replicas with minimal lag»
Aurora supports up to 15 replicas per cluster and, because they read the same volume as the writer instance, the lag is usually tens of milliseconds. The reader endpoint distributes connections among them.
When not: Replicas scale reads, not writes. If the scenario asks to scale writes beyond a single instance, other solutions come into play (such as Aurora PostgreSQL Limitless Database or DynamoDB), not adding replicas.
«low-latency local reads and recovery from the failure of a Region»
Aurora Global Database replicates a cluster to other Regions with a typical lag of under a second, and, if the primary Region fails, a secondary one can be promoted to read/write within minutes.
When not: If you only need high availability within a Region, replicas in multiple AZs are enough. If the application needs to write with low latency in several Regions at once, review the scenario: in Global Database only the primary Region writes.
«storage must grow automatically without provisioning it»
The Aurora volume grows on its own with the data, up to 256 TiB, without you having to reserve storage capacity in advance.
When not: Growing storage is not the same as scaling compute capacity. If the CPU and memory load is unpredictable, the clue points to Aurora Serverless.