What would be best practices for choosing partition/row keys for entities in Azure Tables? The common advice is to magically balance between partition size and number of partitions. But no one seems to have a good definition of how it can be accomplished in 3 easy steps. Is there a general approach for choosing keys so that everything then just works?
There is a detailed article on this very subject up on MSDN: Designing a scalable partitioning strategy for Windows Azure Storage.
I've just recently been looking into the exact same thing and found this good quality article that covers Partition Keys, Row Keys and lots more: Azure Storage Table Design Guide: Designing Scalable and Performant Tables
来源：https://stackoverflow.com/questions/8190349/azure-tables-best-practices-for-choosing-partition-row-keys