A permitting system needs complex multi-table joins and a normalized relational schema. A vendor proposes Amazon DynamoDB as the primary store. What is the sound Cloud Practitioner response?
Select an answer to reveal the explanation.
Short Explanation
DynamoDB is fantastic when you mostly fetch by key, like grabbing a coat by its ticket number. If your app lives on multi-table joins and a classic relational schema, RDS is the better fit. Forcing joins into a key-value world is like using a coat-check for a full accounting ledger.
Full Explanation
Amazon DynamoDB excels at key-value and document access patterns, not as a general substitute for relational schemas that require complex SQL joins. When workloads are relational, Amazon RDS (or Aurora) is the appropriate managed choice. CloudTrail records API activity, and AWS Snowmobile is a large-scale data transfer service—neither is a transactional relational database for permitting joins.