30 |
raised by this ad hoc *data mobility* (see footnote) phenomenon: Dangling links, |
raised by this ad hoc *data mobility* (see footnote) phenomenon: Dangling links, |
31 |
and keeping track of alternative versions. Resolvable location independent identifiers |
and keeping track of alternative versions. Resolvable location independent identifiers |
32 |
make these issues much easier to deal with, since data |
make these issues much easier to deal with, since data |
33 |
can be recognized whereever it is moved. |
can be recognized whereever it is moved. The design also allows for |
34 |
|
automatic balancing of the load, which occurs in location-dependent |
35 |
|
situations with popular items. |
36 |
|
|
37 |
footnote: we emphasize the mobility of *data*. Indeed, technology used |
footnote: we emphasize the mobility of *data*. Indeed, technology used |
38 |
for moving data is not our primary concern. |
for moving data is not our primary concern. In relation to that, the |
39 |
|
mobility of people is obviously a particular reason for data mobility. |
40 |
|
|
41 |
In this paper, we present Storm (for *storage module*), a design |
In this paper, we present Storm (for *storage module*), a design |
42 |
for dealing with these issues. Storm provides an interface to |
for dealing with these issues. Storm provides an interface to |