A Mediator for Approximate Consistency: Supporting “GoodEnough” Materialized Views

  • Authors:
  • Len Seligman;Larry Kerschberg

  • Affiliations:
  • The MITRE Corporation, McLean, VA 22102. E-mail: seligman@mitre.org;George Mason University, Fairfax, VA 22030. E-mail: kersch@gmu.edu

  • Venue:
  • Journal of Intelligent Information Systems
  • Year:
  • 1997

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper addresses the needs of application designers whowould like to tell an automated assistant the following: “Here is aquery that defines a view I want to materialize within myapplication. I need this view to remain approximatelyconsistent with the state of the data sources from which the view isderived, in accordance with declaratively specified stalenesspredicates. When the view becomes stale, follow the refresh strategyI specify (e.g., eager, lazy, hybrid). You must do this inheterogeneous environments containing both active and passive datasources”. This paper describes an architecture that realizes this vision. Theapproach supports materialized, object-based views, called quasi-views, defined over shared databases. Quasi-views arerefreshed according to the consistency conditions and refreshstrategies specified declaratively by application designers. Theseconditions allow for the deviation of quasi-views from their databasecounterparts according to well-defined and monitored approximateconsistency predicates. A layer of software called a Mediator\ for\ Approximate\ Consistencyautomatically generates the databaseobjects necessary to enforce these consistency conditions, shieldingthe application developer from the implementation details ofconsistency maintenance. In addition, it does this for both activeand passive (e.g., legacy) data sources.This paper formalizes quasi-views, presents a declarative quasi-viewspecification language, and describes an architecture andimplementation of a Mediator for Approximate Consistency.