Learning from the past for resolving dilemmas of asynchrony

Ezhilchelvan, PD; Shrivastava, Santosh K.

doi:10.1145/1773912.1773927

Cited by 2 publications

(1 citation statement)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The paper then lays down a convincing rationale for seeking design alternatives to considering asynchronous model augmented with imperfect failure-detectors, and advocates novel ways for building perfect failure detectors. A different strategy is proposed in [10]. Taking a cue from the approach adapted in an earlier system, Total, that made use of LAN broadcast as the transport layer for building total order multicast [31], it proposes using a reliable multi-cast system that offers attainable multi-cast delivery guarantees in probabilistic terms as the transport layer (see [11] for additional details).…”

Section: Responsive Group Communicationmentioning

confidence: 99%

Another look at the middleware for dependable distributed computing

Little

Shrivastava

Wheater³

2011

J Internet Serv Appl

Self Cite

View full text Add to dashboard Cite

Key concepts of reliable distributed computing developed during the 1980s and 1990s (e.g., transactions, replication) influenced the standards based middleware such as CORBA and Java EE. This middleware has evolved steadily over the years with message passing facilities to support construction of loosely coupled systems. However, the way networked computing is being used for business and social uses is undergoing rapid changes as new ways of constructing distributed execution environments from varieties of resources, ranging from computational, storage, network to application level services, provided by globally distributed service providers are emerging. In light of these developments, the paper examines what core concepts, components, and techniques that will be required in the next-generation middleware for dependable distributed computing. The paper puts forward the case for five topics for further research: better coordination facilities for loosely coupled systems, restructuring of the middleware stack for supporting multi-tenancy, replication in the large, negotiation, and enforcement of service agreements, and accountability.

show abstract

Section: Responsive Group Communicationmentioning

confidence: 99%