The cap theorem states that only two of these properties can be simultaneously guaranteed in a distributed service: (i) consistency, (ii) availability and (iii) network partition tolerance. This theorem was stated and...
详细信息
The cap theorem states that only two of these properties can be simultaneously guaranteed in a distributed service: (i) consistency, (ii) availability and (iii) network partition tolerance. This theorem was stated and proved assuming that consistency' refers to atomic consistency. However, multiple consistency models exist and atomic consistency is located at the strongest edge of that spectrum. Many distributed services deployed in cloud platforms should be highly available and scalable. Network partitions may arise in those deployments and should be tolerated. One way of dealing with cap constraints consists in relaxing consistency. Therefore, it is interesting to explore the set of consistency models not supported in an available and partition-tolerant service (cap-constrained models). Other weaker consistency models could be maintained when scalable services are deployed in partitionable systems (cap-free models). Three contributions arise: (i) multiple other cap-constrained models are identified, (ii) a borderline between cap-constrained and cap-free models is set and (iii) a hierarchy of consistency models depending on their strength and convergence is built.
The cap theorem is one example of a more general tradeoff between safety and liveness in unreliable systems. Viewing cap in this context provides insight into the inherent tradeoffs and the manner in which they can be...
详细信息
The cap theorem is one example of a more general tradeoff between safety and liveness in unreliable systems. Viewing cap in this context provides insight into the inherent tradeoffs and the manner in which they can be circumvented in practice.
The cap theorem is used by distributed system practitioners to investigate the necessary trade-offs in the design and development of distributed systems, mainly databases and web applications. In this paper, we use it...
详细信息
ISBN:
(纸本)9781450375689
The cap theorem is used by distributed system practitioners to investigate the necessary trade-offs in the design and development of distributed systems, mainly databases and web applications. In this paper, we use it to reason about access control systems designed for the Internet of Things (IoT). We validate our approach by experimentally investigating alternative architectural designs to enforce access control in a smart lock system using the cloud-edge IoT platform offered by Amazon Web Services. We discuss the trade-off between security and performance that may help IoT designers choose the most suitable architecture supporting their requirements.
At PODC 2000, the cap theorem received its first broad audience. Surprisingly for an impossibility result, one important effect has been to free designers to explore a wider range of distributed systems. Designers of ...
详细信息
ISBN:
(纸本)9781605588889
At PODC 2000, the cap theorem received its first broad audience. Surprisingly for an impossibility result, one important effect has been to free designers to explore a wider range of distributed systems. Designers of wide-area systems, in which network partitions are considered inevitable, know they cannot have both availability and consistency, and thus can now justify weaker consistency. The rise of the "NoSQL" movement ("Not Only SQL") is an expression of this *** choices of how and when to weaken consistency are often the defining characteristics of these systems, with new variations appearing every year. We review a variety of interesting places in the "cap Space" as a way to illuminate these issues and their consequences. For example, automatic teller machines (ATMs), which predate the cap theorem, surprisingly choose availability with weak consistency but with bounded ***, I explore a few of the options to try to "work around" the impossible. The most basic is the use of commutative operations, which make it easy to restore consistency after a partition heals. However, even many commutative operations have non-commutative exceptions in practice, which means that the exceptions may be incorrect or late. Adding the concept of "delayed exceptions" allows more operations to be considered commutative and simplifies eventual consistency during a partition. Furthermore, we can think of delayed exception handling as "compensation" - we execute a compensating transaction that restores *** exception handling with compensation appears to be what most real wide-area systems do - inconsistency due to limited communication is treated as an exception and some exceptional action, such as monetary compensation or even legal action, is used to fix it. This approach to wide-area systems puts the emphasis on audit trails and recovery rather than prevention, and implies that we should expand and formalize the role of compensation in the design of
The global state of a distributed system is most commonly stored in databases. Databases are responsible for ensuring that the data is available, durable, and correct at some level of consistency. However, this approa...
详细信息
Eventual consistency is demanded nowadays in geo-replicated services that need to be highly scalable and available. According to the cap constraints, when network partitions may arise, a distributed service should cho...
详细信息
Eventual consistency is demanded nowadays in geo-replicated services that need to be highly scalable and available. According to the cap constraints, when network partitions may arise, a distributed service should choose between being strongly consistent or being highly available. Since scalable services should be available, a relaxed consistency (while the network is partitioned) is the preferred choice. Eventual consistency is not a common data-centric consistency model, but only a state convergence condition to be added to a relaxed consistency model. There are still several aspects of eventual consistency that have not been analysed in depth in previous works: 1. which are the oldest replication proposals providing eventual consistency, 2. which replica consistency models provide the best basis for building eventually consistent services, 3. which mechanisms should be considered for implementing an eventually consistent service, and 4. which are the best combinations of those mechanisms for achieving different concrete goals. This paper provides some notes on these important topics.
Blockchain is a disruptive technology that relies on the distributed nature of the peer-to-peer network while performing an agreement, or consensus, a mechanism to achieve an immutable, global, and consistent registry...
详细信息
Blockchain is a disruptive technology that relies on the distributed nature of the peer-to-peer network while performing an agreement, or consensus, a mechanism to achieve an immutable, global, and consistent registry of all transactions. Thus, a key challenge in developing blockchain solutions is to design the consensus mechanism properly. As a consequence of being a distributed application, any consensus mechanism is restricted to offer two of three properties: consistency, availability, and partition tolerance. In this paper, we survey the main consensus mechanisms on blockchain solutions, and we highlight the properties of each one. Moreover, we differentiate both deterministic and probabilistic consensus mechanisms, and we highlight coordination solutions that facilitate the data distribution on the blockchain, without the need for a sophisticated consensus mechanism.
Quorum algorithm has become one of the most widely adopted approaches for storing data in the failure-prone distributed storage systems. In this paper, a new approach is proposed which is able to set different levels ...
详细信息
Quorum algorithm has become one of the most widely adopted approaches for storing data in the failure-prone distributed storage systems. In this paper, a new approach is proposed which is able to set different levels of data consistency in key-value NoSQL databases. The proposed approach is based on the parameters set in the NoSQL-dependent structure and is applied to distributed systems, using the quorum algorithm to adjust the consistency and to determine the different grades of data. In this paper, different data writing and reading and mix reading/writing operations are implemented test-bed to study the performance of the proposed approach. In addition to its main goal for improving data consistency, the proposed approach also satisfies the accepted compromise between the pillars of the cap and PACELC theorems. Evaluation of the results shows that the objectives for consistency and efficiency of the proposed approach have been met.
NoSQL databases are designed to address performance and scalability requirements of web based application which cannot be addressed by traditional relational databases. Due to their contrast in priorities and architec...
详细信息
NoSQL databases are designed to address performance and scalability requirements of web based application which cannot be addressed by traditional relational databases. Due to their contrast in priorities and architecture to conventional relational databases using SQL, these databases are referred as "NoSQL" databases since they incorporate lots of additional features in addition to the features of conventional databases. The relational databases strongly follow the ACID (Atomicity, Consistency, Isolation, and Durability) properties while the NoSQL databases follow BASE (Basically Available, Soft State, Eventual consistency) principles. This survey paper is an analytical study on BASE features of some of NoSQL databases. (C) 2015 Elsevier B.V. All rights reserved.
This article provides an overview of current database-management-system technologies and suppliers, along with a case study of an Internet application. The Web Extra at https://***/extra/*** consists of a table descri...
详细信息
This article provides an overview of current database-management-system technologies and suppliers, along with a case study of an Internet application. The Web Extra at https://***/extra/*** consists of a table describing various database management systems.
暂无评论