The access patterns of user requests may be static, so that they do not change over time, or dynamic. It is obviously considerably easier to plan for and manage the static environments than would be the case for dynamic distributed systems. Unfortunately, it is difficult to find many real-life distributed applications that would be classified as static. The significant question, then, is not whether a system is static or dynamic, but how dynamic it is. Incidentally, it is along this dimension that the relationship between the distributed database design and query processing is established.
What does it mean for an access pattern to be "static"? Could you show a practical example of a static access pattern?
Asked By : user1864163
Answered By : AJed
I found what you copied in the following text
The idea is that users access (querying, updating or etc ..) of the database changes with time. It may be at its peaks in sale seasons for example if the database belongs to a commercial applications. etc .. - if it is always fixed and predicted then it is static.
From your copied text: it says that: "it is difficult to find many real-life distributed applications that would be classified as static. The significant question, then, is not whether a system is static or dynamic, but how dynamic it is." --
perhaps, a static access pattern is a collection of sensor nodes that update the database with their readings in a periodic time, with equal size updates always. -- or a set of servers that get a synchronization clock in a periodic manner (quite theoritical i guess)
Best Answer from StackOverflow
Question Source : http://cs.stackexchange.com/questions/7139
0 comments:
Post a Comment
Let us know your responses and feedback