An Essential Design Pattern for Fault-Tolerant Distributed State Sharing.

Saved in:
Bibliographic Details
Title: An Essential Design Pattern for Fault-Tolerant Distributed State Sharing.
Authors: Islam, Nayeem1 nayeem@watson.Ibm.com., Devarakonda, Murthy2 mdev@watson.ibm.com
Source: Communications of the ACM. Oct96, Vol. 39 Issue 10, p65-74. 10p. 6 Graphs.
Subjects: Distributed operating systems (Computers), Fault-tolerant computing, Software patterns, Object-oriented methods (Computer science), Computer software development, Systems design
Abstract: The article focuses on the design and implementation of distributed computer systems. Despite significant common experience and a good deal of success, the cost and complexity of distributed programming continues to be high. Increasingly, project managers look to object-oriented (OO) programming to improve productivity in this area. In order for distributed programming to derive benefits from OO, encouraging the reuse of proven distributed solutions is crucial. In developing distributed programs, successful designers have focused on two important requirements: performance and fault tolerance. Therefore, distributed design patterns should highlight the aspects of a solution that address these requirements. One such OO design pattern, the Recoverable Distributor, allows mixing and matching of fault-tolerance and data-consistency protocols and has been used in a distributed scheduler and a distributed lock manager. Recoverable Distributor is an essential design pattern in fault-tolerant, state-sharing distributed programs. It emphasizes the significance of performance, fault detection, and recovery in such programs. This article presents this pattern and describes how it is used in two commercial distributed programs.
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 12572369
AccessLevel: 6
PubType: Periodical
PubTypeId: serialPeriodical
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: An Essential Design Pattern for Fault-Tolerant Distributed State Sharing.
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Islam%2C+Nayeem%22">Islam, Nayeem</searchLink><relatesTo>1</relatesTo><i> nayeem@watson.Ibm.com.</i><br /><searchLink fieldCode="AR" term="%22Devarakonda%2C+Murthy%22">Devarakonda, Murthy</searchLink><relatesTo>2</relatesTo><i> mdev@watson.ibm.com</i>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Communications+of+the+ACM%22">Communications of the ACM</searchLink>. Oct96, Vol. 39 Issue 10, p65-74. 10p. 6 Graphs.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Distributed+operating+systems+%28Computers%29%22">Distributed operating systems (Computers)</searchLink><br /><searchLink fieldCode="DE" term="%22Fault-tolerant+computing%22">Fault-tolerant computing</searchLink><br /><searchLink fieldCode="DE" term="%22Software+patterns%22">Software patterns</searchLink><br /><searchLink fieldCode="DE" term="%22Object-oriented+methods+%28Computer+science%29%22">Object-oriented methods (Computer science)</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+software+development%22">Computer software development</searchLink><br /><searchLink fieldCode="DE" term="%22Systems+design%22">Systems design</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: The article focuses on the design and implementation of distributed computer systems. Despite significant common experience and a good deal of success, the cost and complexity of distributed programming continues to be high. Increasingly, project managers look to object-oriented (OO) programming to improve productivity in this area. In order for distributed programming to derive benefits from OO, encouraging the reuse of proven distributed solutions is crucial. In developing distributed programs, successful designers have focused on two important requirements: performance and fault tolerance. Therefore, distributed design patterns should highlight the aspects of a solution that address these requirements. One such OO design pattern, the Recoverable Distributor, allows mixing and matching of fault-tolerance and data-consistency protocols and has been used in a distributed scheduler and a distributed lock manager. Recoverable Distributor is an essential design pattern in fault-tolerant, state-sharing distributed programs. It emphasizes the significance of performance, fault detection, and recovery in such programs. This article presents this pattern and describes how it is used in two commercial distributed programs.
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=12572369
RecordInfo BibRecord:
  BibEntity:
    Identifiers:
      – Type: doi
        Value: 10.1145/236156.236172
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 10
        StartPage: 65
    Subjects:
      – SubjectFull: Distributed operating systems (Computers)
        Type: general
      – SubjectFull: Fault-tolerant computing
        Type: general
      – SubjectFull: Software patterns
        Type: general
      – SubjectFull: Object-oriented methods (Computer science)
        Type: general
      – SubjectFull: Computer software development
        Type: general
      – SubjectFull: Systems design
        Type: general
    Titles:
      – TitleFull: An Essential Design Pattern for Fault-Tolerant Distributed State Sharing.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Islam, Nayeem
      – PersonEntity:
          Name:
            NameFull: Devarakonda, Murthy
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 10
              Text: Oct96
              Type: published
              Y: 1996
          Identifiers:
            – Type: issn-print
              Value: 00010782
          Numbering:
            – Type: volume
              Value: 39
            – Type: issue
              Value: 10
          Titles:
            – TitleFull: Communications of the ACM
              Type: main
ResultId 1