Understand your data hotspots -- just because it is in Dynamo and you have moved the slider all the way over to "20,000 IOPS" doesn't mean anything if DDB has p

Understand your data hotspots -- just because it is in Dynamo and you have moved the slider all the way over to "20,000 IOPS" doesn't mean anything if DDB has partitioned all your data into a single shard behind the scenes -- you'll peak at 3,000 IOPS (for example). Unfortunately you _still_ need to be aware of how you plan on querying your data to maximize the performance. This is one of the most common questions/comments I see in the forums. More info: http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GuidelinesForTables.html#GuidelinesForTables.UniformWorkload http://docs.aws.amazon.com/amazondynamodb/latest/developergu... Also be aware that leveraging the Local Secondary Indexes _does_ enforce a 10GB limit on items with the same hashkey, see the last section here: http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GuidelinesForLSI.html http://docs.aws.amazon.com/amazondynamodb/latest/developergu...