Azure Tables: best practices for choosing partition/row keys

Question

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 partiti

Answer 1

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