- Newest
- Most votes
- Most comments
Thanks - we will follow-up with one of our developer evangelists on the best practice here.
Hi @yajaws,
Get the following info from Alex (blog author):
You are correct, some of the issues mentioned in the article are much less critical since the introduction of adaptive capacity, and especially since it became "instant" last year in May: https://aws.amazon.com/about-aws/whats-new/2019/05/amazon-dynamodb-adaptive-capacity-is-now-instant/.
Also, it's worth mentioning that if you are using on-demand pricing you don't even have to worry about capacity at all, so the overhead of splitting into multiple tables may not be worth it.
But, if you are using provisioned capacity you'll need to estimate RCU's and WCU's. In high-throughput scenarios you may still benefit from multiple tables as you don't want writes to be throttled and at the same time you don't want to over-provision reads.
A "hybrid" solution could be enabling on-demand pricing only on older tables whose data is read rarely, and keeping provisioned capacity on the current table where you'll have sustained high-throughput (writes). That should allow you to optimize for cost.
I hope this is useful.
Alex
Thank you very much Arturo and Alex. I am marking your response as helpful and the question as answered. Have a great day.
Edited by: yajaws on Mar 9, 2020 5:17 PM
Edited by: yajaws on Mar 9, 2020 5:18 PM
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago