Flashcards / Architecting: Database Services
← Decks

Architecting: Database Services

8 of 8 cards free · no sign-in needed

CONCEPT
Choosing the right database

Click to reveal answer

ANSWER
Match the data model and access pattern: relational (RDS/Aurora), key-value (DynamoDB), in-memory (ElastiCache), document, graph (Neptune), etc. Purpose-built beats one-size-fits-all.

Click to flip back

  1. Amazon RDS

    Managed relational database supporting MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, and Aurora — AWS handles patching, backups, and failover.

  2. RDS Multi-AZ

    A synchronous standby replica in another AZ that fails over automatically. For high availability — NOT for scaling reads.

  3. RDS read replicas

    Asynchronous read-only copies that scale read traffic and can be promoted to standalone databases. For read scaling, not automatic failover.

  4. Amazon Aurora

    AWS's cloud-native MySQL/PostgreSQL-compatible engine: up to 5×/3× faster, storage auto-scales, and data is replicated six ways across three AZs.

  5. Aurora Serverless v2

    On-demand, auto-scaling Aurora capacity that adjusts in fine-grained increments to match load — for variable or unpredictable workloads.

  6. Amazon DynamoDB

    Fully managed, serverless NoSQL key-value and document database with single-digit-millisecond latency at any scale and automatic scaling.

  7. Data encryption at rest

    RDS and Aurora encrypt storage, snapshots, and replicas using AWS KMS keys; enable at creation for compliance.

🔒

Track what you know

Sign in (free) to flip every card, mark what you know, and pick up exactly where you left off.

Sign in to continueCreate free account

After sign-in: Space flip · ←→ navigate · K knew it · S skip

Other decks you might like

☁️
AWS Practitioner Essentials
10 cards
💰
Cloud Pricing & Billing
15 cards
📋
CLF-C02 Exam Domains
18 cards
cloud
CLF-C02: Introduction to AWS
6 cards