7 ms·
TL;DR - Don't use something as coarse as customer_id as a partition key. Alternatively move to GCP/BigTable. Any DynamoDB tuning advice will say how important
by karmakaze 9y ago
TL;DR - Don't use something as coarse as customer_id as a partition key. Alternatively move to GCP/BigTable.
Any DynamoDB tuning advice will say how important it is to have well distributed hash keys. As for the second part, why not use Cloud Spanner? I wish AWS had something like it.
- deleted 9y ago[deleted]
- nemothekid 9y ago>Any DynamoDB tuning advice will say how important it is to have well distributed hash keys. Maybe I'm missing something, but as I understand it he did have well distributed hash keys (I'm assuming his customer ids were random UUIDs). The problem he had however was that he had so much data that a single custom could cause throughput exceptions on a very small amount of ops/s.
- lotyrin 9y agoCustomer UUID would only be well-distributed for queries of customers. If some customers are more active than others in a given unit time, some customers have more data than others, and customers' data is keyed by customer ID then no, it's not a well distributed key.