Database selection by access pattern · Question 11 of 12
An online retailer has a product catalog with very different attributes and shopping carts with extreme load peaks; both are only read by ID. Orders and invoices need transactions and monthly reports with joins. Which split fits?
2 answers are correct. Hard Created with AI
Show answer
Answer
- D Catalog and shopping carts in DynamoDB with flexible attributes
- E Orders and invoices in Aurora with transactions
Explanation
DynamoDB copes with load peaks for access by key and allows each item to have its own attributes. Transactions across several tables and reports with joins fit Aurora. Memcached loses data when a node fails, and Redshift is built for analytics, not for transactions.