4 ms·
I'm not super familiar with DynamoDB except as a strict key/value store. You set a partition key, you ignore your range key, and you go--what's particularly ove
by eropple 9y ago
I'm not super familiar with DynamoDB except as a strict key/value store. You set a partition key, you ignore your range key, and you go--what's particularly overcomplicated about that?
- paulgb 9y agoIt's been a while since I played around with it but I recall having to increase the number of write nodes to load data at a reasonable rate, then drop the number back down to avoid overpaying. And there were limits on how often you could lower the number of instances so I had to be careful not to reach the limit. Maybe I'm misremembering or that has changed?
- noobiemcfoob 9y agoSetting the number of write nodes and read nodes to match your workload. I was scaling up a system and as more things came online, the traffic became more bursty we were constantly bumping them up and wondering if we were allocating too much (probably useless fretting regardless). Ultimately, we moved to an S3 only solution since we have such a low throughput environment and the simplicity is addictive.
- eropple 9y agoMakes sense in the past, but with DynamoDB autoscaling that's largely gone by the wayside.
- noobiemcfoob 9y agoI hadn't heard about this feature update! Thanks for pointing me at it!