Timedora
Free Online Flashcard Deck

6 Database Selection Case Studies Free Online FlashCards

Study 6 Database Selection Case Studies with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What should guide database selection?

Back

Choose a database by matching its data model and access patterns to requirements such as transactions, consistency, latency, availability, recovery, and operations.

02
Front

When is RDS for PostgreSQL a sensible starting point?

Back

Amazon RDS for PostgreSQL offers a managed service while retaining a familiar relational engine for SQL joins, constraints, and transactions.

03
Front

How does Aurora support read scaling and failover?

Back

Aurora separates shared cluster storage from database instances. Reader instances can serve read traffic, and a reader can take over if the primary becomes unavailable.

04
Front

What kind of workload suits DynamoDB?

Back

DynamoDB suits high-scale key-value or document access, such as retrieving or updating a cart by customer identifier.

05
Front

What is Amazon Redshift best suited for?

Back

Amazon Redshift suits large-scale analytical queries, such as aggregating years of business data for dashboards, rather than serving as the default database for application transactions.

06
Front

How can an e-commerce system divide transaction and cart workloads?

Back

Use Aurora or RDS for orders and inventory when relational constraints and transactions matter; use DynamoDB for carts or sessions with primarily key-based access.

07
Front

What read-replica behavior must RDS applications account for?

Back

RDS read replicas replicate asynchronously, so check whether replica lag is acceptable for queries routed to them.

08
Front

Does an RDS Multi-AZ standby automatically scale reads?

Back

A Multi-AZ standby intended for failover is not automatically a read-scaling replica; capabilities depend on the deployment type and engine.

09
Front

What should be compared before choosing Aurora over RDS?

Back

Compare Aurora and RDS using the actual engine, instance sizes, I/O profile, availability needs, and migration effort; Aurora is not automatically best or least costly.

10
Front

How should DynamoDB keys and indexes be designed?

Back

Design DynamoDB keys and indexes around known queries. For cart items, a customer ID partition key and item identifier sort key can support retrieving and updating a customer’s items.

11
Front

What can a poorly distributed DynamoDB partition key cause?

Back

Poorly distributed partition-key values can create hot partitions, so key design must account for how traffic is distributed.

12
Front

What determines how fresh data is in an analytical warehouse?

Back

Reporting freshness depends on the data-ingestion design. Define acceptable latency and operate the pipeline that delivers data to the warehouse.