Sonntag, 15. April 2012 19:50
Working on a project, where users can create events, and others can attend the events. To model this in Table Storage, my first idea was to model each Event as a seperate partition as this would spread the load on each event. But as each event might have between 10-100 users, this might be a too small partition size.
If I on the otherhand put all events in the same partition, it will not be scaleable or am I missing something?
Sonntag, 15. April 2012 20:27Tiny partitions may not be efficient but are not incorrect and certainly better than too large a partition. So, partition key = event id is quite reasonable.
You may want to also think about deleting events older than a certain date. In that capacity having the event id as a combination of a chronological identifier like year or year + month or date and a base event id could be of value.
Sonntag, 15. April 2012 20:52I will continue in this thread, as the answer might be the same: http://social.msdn.microsoft.com/Forums/en/windowsazuredata/thread/a3172f1d-9188-4651-9907-897a168339a2
Best regards Rasmus Christensen
Montag, 16. April 2012 03:50Moderator
Please refer to another thread you've posted on this forum.
- Als Antwort markiert Rasmus Christensen Sonntag, 22. April 2012 13:03