Skip to main content

dtechbits: CAP Theorem

 

Consistency
Every read receives the most recent write or an error.
Availability
Every request receives a (non-error) response, without the guarantee that it contains the most recent write.
Partition tolerance
The system continues to operate despite an arbitrary number of messages being dropped (or delayed) by the network between nodes.

When a network partition failure happens, it must be decided whether to do one of the following:

  • cancel the operation and thus decrease the availability but ensure consistency
  • proceed with the operation and thus provide availability but risk inconsistency.
CAP Theorem Euler Diagram

Thus, if there is a network partition, one has to choose between consistency or availability. Note that consistency as defined in the CAP theorem is quite different from the consistency guaranteed in ACID database transactions.[4]




Linearizability  or strict consistency: Linear consistency to execute the operations are executed in an order. It provides the definitely updated data as earlier operations are expected to complete atomically inlinear order even though the operations might have done in parallel or concurrently.

Linearizability can be achieved by

1. Distributed locking

2. Two-phase commit

3. Distributed data store with consensus algorithms like Paxos or Raft



PACELC theorem :

The PACELC theorem is an extension of the CAP theorem, providing additional insights into the behaviour of distributed systems during network partitions. The acronym PACELC stands for:

  1. P (Partition tolerance)

  2. A (Availability)

  3. C (Consistency)

  4. E (Else):

    • The "Else" in PACELC suggests that in the absence of network partitions, the system should strive to achieve both consistency and availability. In other words, when the network is not partitioned, the system should aim to be both consistent and available.

  5. L (Latency):

    • PACELC includes an additional factor, "Latency," which highlights the importance of considering the performance characteristics of the system. It emphasises that the system's behaviour during normal operation (without partitions) should also take into account the latency of operations.

  6. C (Complexity):

    • Some versions of the theorem include an additional "C" for "Complexity," which suggests that the decision-making process during network partitions can introduce additional complexity to the system.







Comments

Post a Comment

Popular posts from this blog

React JS Basics

  What are side effects in React? In React, side effects are operations that interact with external systems or cause changes outside the component's rendering process. These can include: Data fetching: Retrieving data from APIs or other sources. Subscriptions: Setting up listeners for events or data changes. Timers: Creating timers for delayed actions or animations. DOM manipulation: Directly modifying the DOM (rarely used in modern React with declarative approach). Why use useEffect ? In class-based components, you would typically use lifecycle methods like componentDidMount , componentDidUpdate , and componentWillUnmount to handle side effects. Functional components don't have these methods directly. The useEffect Hook provides a way to manage side effects in functional components. It allows you to run a function after a component renders (or re-renders) and optionally clean up any resources created by that function before the component unmounts. How does useEffect wor...
Post a Comment
Read more

Difference between SKU and Tenant in multi-tenant SaaS application

SKUs define what you get.  Tenants define who gets it in a securely isolated way. A SaaS provider benefits from SKUs for tiered pricing and multi-tenancy for efficient resource usage.   SKU (Stock Keeping Unit) Features and Pricing: SKUs in a SaaS application typically dictate the set of features, functionalities, and usage limits (e.g., storage, number of users, API call volumes) available to a customer. Customer Choice: Customers choose an SKU based on their needs and budget. Higher-tier SKUs usually offer more capabilities and resources at a higher cost. Within a Tenant: A single tenant (customer) can only be subscribed to one SKU at a time, but may potentially upgrade or downgrade over time. Tenant Data Isolation: A tenant represents a logically isolated instance of the SaaS application dedicated to a specific customer or organization. A customer's data, configurations, and often customizations are kept completely separate from other tenants. Multi-Te...
Post a Comment
Read more

protobuff vs json

  Protocol Buffers (protobuf) and JSON (JavaScript Object Notation) are both data interchange formats, but they have some key differences in terms of usage, efficiency, and features. Here are some points of comparison: Serialization Format: JSON: It's a human-readable, text-based format. It's easy to read and write for both humans and machines. Protobuf: It's a binary serialization format. While it's not human-readable, it's more compact and efficient for data interchange. Data Types: JSON: Supports a limited set of basic data types, including objects, arrays, strings, numbers, booleans, and null. Protobuf: Supports a broader range of data types, including scalar types (integers, floats, booleans, strings), maps, nested structures, and more. Schema: JSON: Schema is not explicitly defined, which means there is flexibility but less strict validation. Protobuf: Requires a predefined schema (defined in a .proto file). This schema provides a contract for the data s...
Post a Comment
Read more