Table design guidelines
When designing your tables, you should be able to get the most out of the Table storage service in order to achieve and meet your goals. Tables are mostly used for intensive read and write operations, with the ability to scale up as much as needed; thus your design must be tailored to meet your needs and your scenarios.
Things to keep in mind to design read-efficient tables:
When designing for heavy read-querying applications, it is recommended to think about how you will query your data in the most performant way before even thinking how you will be modifying your data.
Note
For example, the previous weather table design was built around the fact that weather is mostly requested by city and by date.
As Table storage is relatively cheap, consider the option of storing duplicate copies of your entities with different keys, since the best queries are the ones that specify both the PartitionKey and RowKey, called point queries. In our previous example, we can save a duplicate...
