If we add more and more users into database. I guess we should re-partition the database. Is this partition static or dynamic?
ferozenaina
That would depend on how you partition the database. Using dynamic re-partitioning would be good when we don't know the distribution of incoming data. I'm not sure how it would be implemented.
In practice, I think they would use static partitioning with userID or numbers, storing a range of numbers in one database. Since this number is fixed once, they wouldn't have to dynamically re-partition. When more users are added with increasing userIDs, they would provision more database instances to handle the new user data.
If we add more and more users into database. I guess we should re-partition the database. Is this partition static or dynamic?
That would depend on how you partition the database. Using dynamic re-partitioning would be good when we don't know the distribution of incoming data. I'm not sure how it would be implemented.
In practice, I think they would use static partitioning with userID or numbers, storing a range of numbers in one database. Since this number is fixed once, they wouldn't have to dynamically re-partition. When more users are added with increasing userIDs, they would provision more database instances to handle the new user data.