Explore chapters and articles related to this topic
Databases
Published in Ian Foster, Rayid Ghani, Ron S. Jarmin, Frauke Kreuter, Julia Lane, Big Data and Social Science, 2020
An important result in distributed systems (the so-called “CAP theorem,” Brewer, 2012) observes that it is not possible to create a distributed system with all three properties. This situation creates a challenge with large transactional data sets. Partitioning and replication are needed in order to achieve high performance, but, as the number of computers grows, so too does the likelihood of network disruption among pair(s) of computers. A network disruption can prevent some replicas of a data item from being updated, compromising consistency. Because strict consistency cannot be achieved at the same time as availability and partition tolerance, the DBMS designer must choose between high consistency and high availability for a particular system.
Cloud Computing
Published in Vivek Kale, Digital Transformation of Enterprise Architecture, 2019
The CAP theorem implies that consistency guarantees in large-scale distributed systems cannot be as strict as those in centralized systems. Specifically, it suggests that distributed systems may need to provide BASE guarantees instead of the ACID guarantees provided by traditional database systems. The CAP theorem states that no distributed system can provide more than two of the following three guarantees: consistency, availability, and partitioning-tolerance. Here, consistency is defined as in databases; i.e., if multiple operations are performed on the same object (which is actually stored in a distributed system), the results of the operations appear as if the operations were carried out in some definite order on a single system. Availability is defined to be satisfied if each operation on the system (e.g., a query) returns some result. The system provides partitioning-tolerance if the system is operational even when the network between two components of the system is down.
Mission-Critical Cloud Computing for Critical Infrastructures
Published in David Bakken, Krzysztof Iniewski, Smart Grids, 2017
Thoshitha Gamage, David Anderson, David Bakken, Kenneth Birman, Anjan Bose, Carl Hauser, Ketan Maheshwari, Robbert van Renesse
PaaS for the power grid will need to encompass industry best practices, engineering standards, compliance requirements, and data privacy and security requirements as properties of the platform itself. The CAP theorem [7] argues that simultaneously achieving three key properties—consistency, availability, and partition tolerance—is impossible in distributed systems. As a result, and especially since their apps are not mission critical, present-day commercial clouds often sacrifice consistency in favor of availability. Cloud environments that are used for power applications must be able to guarantee high-assurance properties, including consistency, fault tolerance, and real-time responsiveness, in order to support the anticipated needs of power applications.
Blockchain Adoption from an Interorganizational Systems Perspective – A Mixed-Methods Approach
Published in Information Systems Management, 2021
Flynn Werner, Marcus Basalla, Johannes Schneider, Demelza Hays, Jan Vom Brocke
As these properties directly apply to blockchain technology and are also present in general database systems literature (Elmasri & Navathe, 2010) we chose them for our further analysis. According to the CAP theorem (Brewer, 2010), the core properties of distributed database systems are consistency, availability, and partitioning. As blockchain constitutes a distributed system and can be seen as a competitor to currently used distributed database systems, we also included these three properties in our analysis. As blockchain technology constitutes a multi-user system we selected concurrency as a tenth property, as the textbook on database systems by Elmasri and Navathe (2010) stresses the importance of this property for multi-user systems.