By Topic

Rethinking integrity [distributed databases]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Ammann, P. ; George Mason Univ., Fairfax, VA, USA ; Jajodia, S.

In practice, no real database enjoys complete integrity, a variety of factors conspire to make some information stale, missing, or just plain wrong. System design and analysis should recognize that real systems lack integrity to some degree, most, if not all, of the time. Significant benefits flow from such recognition. Risk management techniques can identify the severity of different integrity-loss scenarios, thereby focusing scarce resources on critical areas. A designer can deliberately sacrifice nonessential integrity under carefully controlled conditions to achieve other design objectives, such as performance, autonomy, availability, or security. Designers can achieve these objectives and still preserve essential aspects of integrity. The authors discuss the factors that undermine integrity in distributed databases

Published in:

Concurrency, IEEE  (Volume:5 ,  Issue: 4 )