Improving Availability in Distributed Tuple Spaces Via Sharing Abstractions and Replication Strategies

Vitaly Buravlev, Rocco De Nicola, Alberto Lluch Lafuente, Claudio Antares Mezzina

Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review

Abstract

Data availability is a key aspect of modern distributed systems. We discuss an extension of coordination languages based on tuple spaces with programming abstractions for sharing data and guaranteeing availability with different consistency guarantees. Data can be spread over the system according to user-specified replica placement strategies and user-specified consistency requirements. The framework takes care then of low-level management of the replicas, so that the programmer can just focus on the business logic of the application. We advocate that the proposed programming primitives are beneficial for data-oriented applications where different kinds of data may have different needs in terms of availability and consistency.
Original languageEnglish
Title of host publicationProceedings of 2018 26th Euromicro International Conference on Parallel, Distributed and Network-based Processing (PDP)
PublisherIEEE
Publication date2018
Pages302-5
ISBN (Print)978-1-5386-4975-6
DOIs
Publication statusPublished - 2018
Event26th Euromicro International Conference on Parallel, Distributed and Network-based Processing - Cambridge, United Kingdom
Duration: 21 Mar 201823 Mar 2018
Conference number: 26

Conference

Conference26th Euromicro International Conference on Parallel, Distributed and Network-based Processing
Number26
Country/TerritoryUnited Kingdom
CityCambridge
Period21/03/201823/03/2018

Bibliographical note

See details at https://ieeexplore.ieee.org/document/8374475/

Keywords

  • Tuple Spaces
  • Dynamic replication
  • Data consistency
  • Network

Fingerprint

Dive into the research topics of 'Improving Availability in Distributed Tuple Spaces Via Sharing Abstractions and Replication Strategies'. Together they form a unique fingerprint.

Cite this