Azure的表：最佳做法，选择分区/行键 [英] Azure Tables: best practices for choosing partition/row keys

问题描述

但为啥要选择分区/行键在Azure的表实体最佳做法？常见的建议是分区的大小和分区的数量之间的平衡神奇。但似乎没有人对如何能在3个简单的步骤来完成一个很好的定义。是否有选择键，以便一切都那么只是工作的一般方法？

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?

推荐答案

有上这个主题了MSDN上详细的文章，设计用于Windows Azure存储一个可扩展的分区策略：<一href=\"http://msdn.microsoft.com/en-us/library/hh508997.aspx\">http://msdn.microsoft.com/en-us/library/hh508997.aspx

There is a detailed article on this very subject up on MSDN, "Designing a scalable partitioning strategy for Windows Azure Storage" : http://msdn.microsoft.com/en-us/library/hh508997.aspx

这篇关于Azure的表：最佳做法，选择分区/行键的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！