Replicated data management for mobile computing

• Main Author: Terry, Douglas B.
• Corporate Author: Morgan & Claypool Publishers.
• Format: Electronic
• Language: English
• Published: San Rafael, Calif. (1537 Fourth Street, San Rafael, CA 94901 USA) : Morgan & Claypool Publishers, c2008.
• Series: Synthesis lectures in mobile and pervasive computing ; #5.
• Subjects: Cache memory.; Data transmission systems.; Database management.; Mobile computing.; Ubiquitous computing.
• Online Access: Abstract with links to full text
• Item Description: Part of: Synthesis digital library of engineering and computer science.; Series from website.; Title from PDF t.p. (viewed on Oct. 10, 2008).
• Physical Description: 1 electronic document (xi, 93 p.) : digital file.; Available also in print.
• Format: Mode of access: World Wide Web.; System requirements: PDF reader.
• Bibliography: Includes bibliographical references (p. 83-91).
• ISBN: 159829203X (electronic bk.); 9781598292039 (electronic bk.)
• Access: Abstract freely available; full-text restricted to subscribers or individual document purchasers.

Managing data in a mobile computing environment invariably involves caching or replication. In many cases, a mobile device has access only to data that is stored locally, and much of that data arrives via replication from other devices, PCs, and services. Given portable devices with limited resources, weak or intermittent connectivity, and security vulnerabilities, data replication serves to increase availability, reduce communication costs, foster sharing, and enhance survivability of critical information. Mobile systems have employed a variety of distributed architectures from client-server caching to peer-to-peer replication. Such systems generally provide weak consistency models in which read and update operations can be performed at any replica without coordination with other devices. The design of a replication protocol then centers on issues of how to record, propagate, order, and filter updates. Some protocols utilize operation logs, whereas others replicate state. Systems might provide best-effort delivery, using gossip protocols or multicast, or guarantee eventual consistency for arbitrary communication patterns, using recently developed pairwise, knowledge-driven protocols. Additionally, systems must detect and resolve the conflicts that arise from concurrent updates using techniques ranging from version vectors to read-write dependency checks. This lecture explores the choices faced in designing a replication protocol, with particular emphasis on meeting the needs of mobile applications. It presents the inherent trade-offs and implicit assumptions in alternative designs. The discussion is grounded by including case studies of research and commercial systems including Coda, Ficus, Bayou, Sybase's iAnywhere, and Microsoft's Sync Framework.