Re:The DynamoDB Book: Data Modeling with NoSQL and DynamoDB
by luhn on Friday May 15, 2020 @01:30PM
(#23194826)
As of a couple years ago, DynamoDB will redistribute throughput between shards based on usage [1], so in theory this should eliminate the hot shard problem. I haven't had a chance to test this in practice, if anybody has hands-on experience I'd love to hear it.
You also finally have a way of identifying hot keys with the terribly named CloudWatch Contributor Insights for DynamoDB. [2]
For exceptional use cases, you also have the option of On-Demand Capacity to pay for what you use and not worry about capacity at all. [3]
[1] https://docs.aws.amazon.com/amazondynamodb/latest/developerg...
[2] https://docs.aws.amazon.com/amazondynamodb/latest/developerg...
[3] https://docs.aws.amazon.com/amazondynamodb/latest/developerg...
Re:The DynamoDB Book: Data Modeling with NoSQL and DynamoDB
by eloff on Friday May 15, 2020 @01:35PM
(#23194899)
That sounds like the problem had been solved and my information is just out of date now. Maybe I should give DynamoDB another look now.
Re:The DynamoDB Book: Data Modeling with NoSQL and DynamoDB
by Judson on Friday May 15, 2020 @01:32PM
(#23194859)
With instant adaptive capacity, I think quite a few hot key issues are mitigated.
https://aws.amazon.com/blogs/database/how-amazon-dynamodb-ad...
Re:The DynamoDB Book: Data Modeling with NoSQL and DynamoDB
by abd12 on Friday May 15, 2020 @04:13PM
(#23196857)
luhn responded to this one pretty well :)
Basically, most of these issues are gone. As long as you don't have extreme skew in your partition keys, you don't need to worry about throughput limits.
[1] https://syslog.ravelin.com/you-probably-shouldnt-use-dynamod...