skip to main content
article
Free Access

Data replicas in distributed information services

Published:01 March 1989Publication History
Skip Abstract Section

Abstract

In an information distribution network in which records are repeatedly read, it is cost-effective to keep read-only copies in work locations. This paper presents a method of updating replicas that need not be immediately synchronized with the source data or with each other. The method allows an arbitrary mapping from source records to replica records. It is fail-safe, maximizes workstation autonomy, and is well suited to a network with slow, unreliable, and/or expensive communications links.

The algorithm is a manipulation of queries, which are represented as short encodings. When a response is generated, we record which portion of the source database was used. Later, when the source data are updated, this information is used to identify obsolete replicas. For each workstation, the identity of obsolete replicas is saved until a workstation process asks for this information. This workstation process deletes each obsolete replica, and replaces it by an up-to-date version either promptly or the next time the application asks for this particular item. Throughout, queries are grouped so that the impact of each source update transaction takes effect atomically at each workstation.

Optimizations of the basic algorithm are outlined. These overlap change dissemination with user service, allow the mechanism to be hidden within the data delivery subsystem, and permit very large networks.

References

  1. 1 ADIBA, M. E., AND LINDSAY, B.G. Database Snapshots, IBM Research Report RJ2772, 1980.Google ScholarGoogle Scholar
  2. 2 BERNSTEIN, P. A., AND GOODMAN, N. Concurrency control in distributed database systems. Comput. Surv. 13, 1 (1981), 185-221. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. 3 ESWARAN, K. P., GRAY, J. N., LORIE, R. A., AND TRAIGER, I.L. The notions of consistency and predicate locks in a database system. Commun. ACM 19, 11 (1976), 624-633. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. 4 GARCIA-MOLINA, H., AND WIEDERHOLD, G. Read-only transactions in a distributed database. ACM Trans. Database Syst. 7, 2 (1982), 209-304. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. 5 GLADNEY, H.M. A model for distributed information networks. IBM Res. Rep. RJ5220, 1986. Available from the librarian at the IBM Almaden Research Center.Google ScholarGoogle Scholar
  6. 6 GLADNEY, H. M., ARTSY, Y., AND CHANG, H.Y. Note: File synchronization in weakly coupled networks. IBM Res. Rep. RJ5043, 1985.Google ScholarGoogle Scholar
  7. 7 INTERNATIONAL BUSINESS MACHINES. SQL/Data System. IBM Program Product 5748-XXJ, 1983.Google ScholarGoogle Scholar
  8. 8 IVES, B., AND LEARMONTH, G.P. The information system as a competitive weapon. Commun. ACM 27, 12 (1984), 1193-1201. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. 9 LANDERS, T., AND ROSENBERG, R.L. An overview of MULTIBASE. In Distributed Data Bases. Proceedings of Second International Symposium on Distributed Data Bases. H. J. Schneider, Ed., North-Holland, Amsterdam, The Netherlands, Sept. 1982.Google ScholarGoogle Scholar
  10. 10 LINDSAY, B., HAAS, L. M., MOHAN, C., PIRAHESH, H., AND WILMS, P. A snapshot differential refresh algorithm. IBM Res. Rep. RJ4992, 1986. Also in ACM Proceedings SIGMOD 15, 2 (1986), 53-60. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. 11 LOHMAN, G. M., MOHAN, C., HAAS, L. M., LINDSAY, B. G., SELINGER, P. G., AND WILMS, P.F. Query processing in R*, IBM Research Report RJ4272, 1984.Google ScholarGoogle Scholar
  12. 12 MALHOTRA, A., MARKOWITZ, H. M., AND PAZEL, D.P. Consistent copy: A new database facility, IBM Research Report RC9630, 1982.Google ScholarGoogle Scholar
  13. 13 MATTSON, R. L. ET AL. VIEW & SHOP prototype, 1983-84.Google ScholarGoogle Scholar
  14. 14 MOHAN, C. Recent and future trends in distributed data base management. IBM Res. Rep. RJ4240, 1984.Google ScholarGoogle Scholar
  15. 15 MORRIS, J. H., SATYANARANYANAN, M., CONNER, U. D., HOWARD, J. H., ROSENTHAL, D. S. H., AND SMITH, F. D. Andrew: A distributed personal computing environment. Commun. ACM 29, 3, 184-201, 1986. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. 16 ROTHNIE, J. B., BERNSTEIN, P. A., FOX, S., GOODMAN, N., HAMMER, M., LANDERS, T. A., REEVE, C., SHIPMAN, D. W., AND WONG, S. Introduction to a system for distributed databases (SDD-1), ACM Trans. Database Syst. 5, 1 (1980), 1-17. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. 17 SCHMIDT, E.E. Controlling Large So{tware Development in a Distributed Environment. Ph.D. dissertation, University of California at Berkeley, 1982. Also appeared as Xerox PARC report CSL-82-7. Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. 18 SMITH, M. D., ED. The Ortho Problem Solver. Ortho Information Services, San Francisco, 1982.Google ScholarGoogle Scholar
  19. 19 SUNSET MAGAZINE EDITORS. Western Garden Book, Lane Magazine and Book Co., Menlo Park, Cal., i970.Google ScholarGoogle Scholar
  20. 20 TRAIGER, I. L., GRAY, J. N., GALTIERI, C. A., AND LINDSAY, B.G. Transactions and consistency in distributed database systems. ACM Trans. Database Syst. 7, 3 (1982), 323-342. Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. 21 Yv, C. T., AND CHANG, C. C. On the Design of a Query Strategy in a Distributed Database Environment. ACM Proceedings of SIGMOD 15, 2 (1983), 30-39. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Data replicas in distributed information services

        Recommendations

        Reviews

        Mark S. Day

        This work describes what seems to be a useful, reasonable algorithm for updating replicas in situations where the replicas “need not be immediately synchronized with the source data or with each other.” Readers interested in the practical applicability of this algorithm will do well to skip past its formal presentation on first reading, since it is difficult to see the significance of many of the algorithm's features outside the context of an application. In several places, the paper goes from a vague definition of a problem to a formal statement of a solution (without an intervening level that explains the approach being taken). For example, the given time line and definitions relating points on that time line seem much more significant and complicated than what they are: essentially a formalization of the notion that “database time” is determined by timestamps rather than physical time. These problems are flaws only in the presentation, however, not in the ideas.

        Access critical reviews of Computing literature here

        Become a reviewer for Computing Reviews.

        Comments

        Login options

        Check if you have access through your login credentials or your institution to get full access on this article.

        Sign in

        Full Access

        • Published in

          cover image ACM Transactions on Database Systems
          ACM Transactions on Database Systems  Volume 14, Issue 1
          March 1989
          146 pages
          ISSN:0362-5915
          EISSN:1557-4644
          DOI:10.1145/62032
          Issue’s Table of Contents

          Copyright © 1989 ACM

          Publisher

          Association for Computing Machinery

          New York, NY, United States

          Publication History

          • Published: 1 March 1989
          Published in tods Volume 14, Issue 1

          Permissions

          Request permissions about this article.

          Request Permissions

          Check for updates

          Qualifiers

          • article

        PDF Format

        View or Download as a PDF file.

        PDF

        eReader

        View online with eReader.

        eReader