What is the best table design if I want to use Azure Table Service for a simple social networking website?
- The website could have millions of users.
- Users need to be able to view a list of all other users in the system sorted by the number of mutual connections.
- Users must be able to view a list of their connections
- User must be able to view content posted by themselves and their connections.
One major design constraint is that Azure table service queries are generally limited to the partition key and row key when there are a large number of records or else they get really slow. Another constraint is that query results are only sorted by the partition key and then the row key.
- Edited by Xethnic Saturday, January 24, 2015 8:28 PM