A team debates one DynamoDB table with careful keys versus many tables that mirror a relational permits schema. What modeling guidance should developers follow?
Select an answer to reveal the explanation.
Short Explanation
DynamoDB isn’t a tiny SQL clone. Design keys for how the permit app actually reads and writes—often one table plus GSIs—not one DynamoDB table per old ERD box.
Full Explanation
Effective DynamoDB modeling starts from access patterns. Single-table designs with composite keys and GSIs are common for related entities queried together. Naively mirroring each relational table loses that advantage; GSIs remain useful; extreme SQL normalization is not the DynamoDB starting point.