Re:From relational DB to a single DynamoDB table
by mabbo on Friday January 04, 2019 @01:02PM
(#18826136)
Not exactly. If you find yourself needing to do multiple reads for the same record then whichever row you loaded first, put the other data into that same row. It's all about planning your access patterns ahead of time.
You also very likely need to use DynamoDB transactions (not really mentioned in the article) or else you're taking big integrity risks with partially incoherent records and so you're paying more for their transaction bookkeeping as well.
Doesn't this seem to map badly to DynamoDB's cost model?