Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A distributed system is a group of independent computers that coordinates over a network to provide one service. Because messages can be delayed, lost, reordered or split by a partition—and machines can fail independently—the central design problem is deciding which guarantees to preserve when coordination is difficult.

What is a distributed system?

A distributed system coordinates multiple processes running on separate computers. To a user, those computers may appear to be one database, service, storage platform or application.

The computers exchange messages rather than sharing memory. That makes ordinary single-machine assumptions unsafe: a response may be slow because a machine is overloaded, absent because a link failed, or duplicated because a retry arrived after the original request succeeded.

Distributed-systems courses commonly organize the subject around distributed computation, remote procedure calls (RPC), failure models, clocks, mutual exclusion, consensus, transactions, consistency, scheduling and model checking. Those topics are connected: a choice about timeouts or ordering can change the consistency and recovery behavior of the entire service.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
#1 Best Overall
Elebase USB to USB C Adapter for iPhone 18 Pro Max,USBC Car Charger Adapter
  • Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
  • Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
  • Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
  • Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
  • 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.

Why the network creates hard problems

Delay and slow responses

A message that has not arrived may be lost, delayed, or still being processed. A timeout is therefore an inference, not proof that the remote operation failed.

Loss and reordering

Messages can disappear or arrive in a different order from the one in which they were sent. Protocols need sequence information, acknowledgements or other rules to decide which messages are valid.

Independent machine failures

One process can crash while its peers continue. A service must decide whether to fail over, wait for recovery, or reject work that cannot be made safe.

Network partitions

A partition prevents groups of healthy machines from communicating. Each side may still be running, but neither can assume that the other side has seen the latest state.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Different failure models

Designs must state what kind of failure they tolerate:

Rank #2
Anker USB-C Hub, 5-in-1 USB Hub for Laptops, 4K HDMI Multiport Adapter
  • 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
  • 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
  • Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
  • 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
  • What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
  • Crash failure: a process stops responding.
  • Network failure: messages are lost or a path is unavailable.
  • Timing failure: a process responds too slowly to meet the protocol’s deadline.
  • Byzantine failure: a faulty participant sends arbitrary or conflicting information.

Synchronous and asynchronous models make different assumptions about known time bounds. Consensus and failure-detector results depend on those assumptions; a protocol that is safe under crash failures is not automatically safe against Byzantine behavior.

Replication and consistency are different

Replication means keeping copies of data or service state on multiple nodes. Copies can improve durability and allow a service to continue when one node fails. They also create a coordination problem: replicas need rules for ordering updates, deciding which members are current and repairing lagging state.

Consistency describes what readers are allowed to observe while those copies change. Replication is an implementation technique; consistency is a user-visible guarantee.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Common consistency semantics

Semantic Reader-visible guarantee Typical trade-off
Linearizable Each operation appears to take effect at one instant, respecting real-time order; a read returns the latest completed write or an error. Usually requires coordination and can sacrifice availability during a partition.
Sequential All operations can be placed in one global order that preserves each process’s own order, without requiring real-time order across processes. Weaker than linearizability, but still needs a global ordering mechanism.
Causal Operations related by cause and effect are observed in that order; concurrent operations may be seen in different orders. Can reduce coordination compared with a single total order, but applications must tolerate concurrent results.
Eventual If updates stop and communication resumes, replicas converge; a read may temporarily return stale or divergent data. Often supports low-latency, highly available serving at the cost of immediate-read guarantees.

The right semantic depends on the operation. A lock service or membership registry generally needs a stronger ordering guarantee than a cache or an asynchronously replicated feed.

What CAP theorem actually says

CAP concerns three properties:

  • Consistency: each read receives the most recent write or an error.
  • Availability: every request receives a non-error response.
  • Partition tolerance: the system continues operating despite arbitrary loss of messages between nodes.

When a partition occurs, a design cannot simultaneously keep serving every request and guarantee that every successful read reflects one current order of writes. It must either reject or delay some operations for stronger consistency, or continue serving responses that may be stale or divergent.

Rank #3
Sale
Anker USB C Hub, 7in1 Multi-Port USB Adapter, 4K@60Hz USBC to HDMI Splitter
  • Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
  • Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
  • Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
  • Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
  • What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.

“Pick two” is therefore an incomplete slogan. In a real network, partitions are a failure condition you must address. CAP describes the choice made during that condition; it does not say that a system permanently lacks one of the three properties in normal operation. It also does not replace a precise consistency specification such as linearizable, causal or eventual consistency.

How fault tolerance and quorums work

Fault tolerance uses redundancy so that another subsystem can assume work when one fails. Replicas, health checks, failover and state repair are common parts of that design.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Crash-failure quorum sizing

Google SRE describes the common majority rule: 2f + 1 replicas can tolerate f crash failures. A majority is required to make progress and to prevent two conflicting majorities from being accepted at once. The formula assumes the failure model and quorum protocol actually use those intersections.

Byzantine-failure sizing

For Byzantine fault tolerance, Google SRE gives the common requirement of 3f + 1 replicas to tolerate f Byzantine-faulty replicas. Byzantine protocols need additional message validation and quorum rules because a faulty participant may lie rather than simply stop.

Failure assumption Common replica count What the figure means
Crash failures 2f + 1 Tolerates up to f crashed replicas under a majority-quorum protocol; Google SRE, 2017.
Byzantine failures 3f + 1 Common requirement to tolerate f arbitrary or malicious replicas; Google SRE, 2017.

Replica count alone does not guarantee availability. Placement across failure domains, network reachability, membership changes, storage durability and the recovery procedure all matter.

Rank #4
Sale
UGREEN USB to USB C Adapter Combo 4-Pack, 10Gbps USB C Converter Space Gray
  • Dual Converters, Infinite Potential:Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
  • Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
  • Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
  • Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
  • Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft

What Paxos and Raft are used for

Paxos and Raft are consensus approaches. Consensus lets distributed participants agree on a value or an ordered sequence of values despite specified failures. A primary use is state-machine replication: each replica applies the same deterministic commands in the same order, producing equivalent state.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The basic consensus workflow

  1. A client submits a command to a node that can coordinate the group.
  2. The protocol proposes an ordered entry and exchanges messages with other replicas.
  3. A quorum accepts the entry according to the protocol’s rules.
  4. Replicas apply the committed entries to their state machines and can acknowledge the result.
  5. A recovering or newly added replica obtains missing state through log replay or state transfer.

Practical consensus designs also need recovery and reconfiguration: they must define how a node catches up, how membership changes safely, and what happens when a coordinator fails. Microsoft Research frames consensus specifically as a basis for state-machine replication and covers Paxos, recovery, state transfer and reconfiguration.

Paxos and Raft in practice

Paxos is a family of consensus protocols traditionally presented through numbered proposals and acceptors. Raft presents the same core problem with an intentionally structured replicated log, explicit leadership and terms, making its roles and recovery behavior easier for many teams to explain and implement. Neither protocol removes the need to choose timeouts, deploy replicas across failure domains, monitor lag and handle membership changes.

Consensus is not a universal performance solution. Google SRE notes that no single consensus or state-machine-replication algorithm is best for every workload: performance depends on workload, objectives and deployment.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

RPC, timeouts and retries: the first operational trap

RPC makes a remote call look like a local function, but the failure behavior is different. If a client times out, it cannot know whether the server rejected the request, never received it, or completed it just before the response was lost.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Best Value
Anker USB C Hub, 5-in-1 USBC to HDMI Splitter with 4K Display
  • 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
  • Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
  • Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
  • HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
  • What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.

Blind retries can therefore execute a non-idempotent operation twice. Safer designs specify which operations are idempotent, attach request or deduplication identifiers where appropriate, apply bounded retry and backoff policies, and expose enough logging and metrics to distinguish server failure from network delay.

Timeouts should reflect the service’s latency objective and dependency chain. A timeout that is too short creates avoidable retries; one that is too long ties up resources and delays failover.

How to compare distributed-system designs

Do not compare systems by replica count or a CAP label alone. Evaluate the guarantees and costs that affect your workload.

Question Why it matters
What consistency is promised? Determines whether stale, reordered or conflicting reads are acceptable.
What happens during a partition? Shows which requests are rejected, delayed or served with weaker freshness.
What is the latency target? Quorum round trips and cross-region coordination add delay.
Where are replicas placed? Placement determines whether a zone, region or link failure removes a quorum.
Which failures are covered? Crash, timing, network and Byzantine assumptions require different protocols.
How is membership changed? Unsafe reconfiguration can create split-brain or lose the authoritative state.
How is recovery verified? Backups, logs, state transfer and repair determine whether a failed node can safely return.
What is the operational burden? Monitoring, capacity planning, incident procedures and model checking are part of the system’s real cost.

A practical learning sequence

  1. Model processes, messages, clocks and failures. Start by stating what can be delayed, lost, reordered or corrupted.
  2. Learn RPC and timeouts. Trace a request, timeout and retry, including the possibility that the first request completed.
  3. Study replication and consistency. Compare linearizable, sequential, causal and eventual behavior using the same read and write examples.
  4. Learn consensus and state-machine replication. Work through Paxos and Raft concepts, quorum intersections, recovery and reconfiguration.
  5. Add transactions and recovery. Study atomic commit, durable logging, repair and the limits of coordinating multiple services.
  6. Measure and verify. Use observability, scheduling experiments and model checking to test failure scenarios rather than relying on a happy-path diagram.

Harvard’s CS 2620 curriculum includes consensus, the FLP impossibility result, Paxos, state-machine replication, Multi-Paxos and PBFT. Columbia’s distributed-systems curriculum extends through transactions, consistency, scheduling and model checking. Together, those topics provide a progression from failure models to production-level reasoning.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Checklist before calling a design “distributed” and resilient

  • Have you documented the process, message and clock model?
  • Can you distinguish a crash from a slow response or a partition?
  • Is the consistency guarantee written in terms an application can test?
  • What does each client do after a timeout?
  • Can retries duplicate work, and how are duplicates handled?
  • Which quorum is required for reads, writes and membership changes?
  • What happens when the system loses exactly one node, a majority, or an entire failure domain?
  • How does a returning replica catch up before serving traffic?
  • What evidence shows that recovery and failover work under load?

Bottom line

Distributed systems are not simply “many servers.” They are agreements among independent machines operating with incomplete information. Replication supplies redundancy, consistency defines what users observe, CAP explains the partition-time trade-off, and consensus supplies a safe way to order shared state under stated failure assumptions. A robust design makes each assumption explicit, then tests the recovery path as seriously as the normal path.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.