Hubbry Logo
search button
Sign in
Network partition
Network partition
Comunity Hub
History
arrow-down
starMore
arrow-down
bob

Bob

Have a question related to this hub?

bob

Alice

Got something to say related to this hub?
Share it here.

#general is a chat channel to discuss anything related to the hub.
Hubbry Logo
search button
Sign in
Network partition
Community hub for the Wikipedia article
logoWikipedian hub
Welcome to the community hub built on top of the Network partition Wikipedia article. Here, you can discuss, collect, and organize anything related to Network partition. The purpose of the hub is to conne...
Add your contribution
Network partition

A network partition is a division of a computer network into relatively independent subnets, either by design, to optimize them separately, or due to the failure of network devices. Distributed software must be designed to be partition-tolerant, that is, even after the network is partitioned, it still works correctly.

For example, in a network with multiple subnets where nodes A and B are located in one subnet and nodes C and D are in another, a partition occurs if the network switch device between the two subnets fails. In that case nodes A and B can no longer communicate with nodes C and D, but all nodes A-D work the same as before.

As a CAP trade-off

[edit]

The CAP theorem is based on three trade-offs: consistency, availability, and partition tolerance. Partition tolerance, in this context, means the ability of a data processing system to continue processing data even if a network partition causes communication errors between subsystems.[1]

[edit]

References

[edit]
  1. ^ Stonebraker, Michael (April 5, 2010). "Errors in Database Systems, Eventual Consistency, and the CAP Theorem". Communications of the ACM. Archived from the original on January 23, 2015.