What Makes a System Distributed?
What you'll learn: The defining characteristics that make a system "distributed" rather than simply concurrent or parallel.
The Core Idea
A distributed system is a collection of independent computers that work together to appear as a single coherent system to users. Unlike concurrent or parallel programs running on one machine, distributed systems span multiple separate machines (nodes) connected by a network.
Think of it like a group project where team members work from different cities. They can't share the same desk or whiteboard — instead, they must communicate by phone, email, or video chat. Each person works independently, but they coordinate to produce a unified result.
Key Characteristics
Multiple Autonomous Nodes
Each computer in a distributed system operates independently with its own processor, memory, and operating system. These nodes can fail, restart, or operate at different speeds without bringing down the entire system.
Message Passing
Since nodes don't share physical hardware, they communicate by sending messages over a network. This introduces latency, potential message loss, and ordering challenges that don't exist in single-machine programs.
No Shared Memory
Unlike threads on one machine that can directly read and write shared memory, distributed nodes have completely separate memory spaces. They can only learn about each other's state through explicit communication.
Why It Matters
These three characteristics create unique challenges: network failures can partition the system, messages can arrive out of order or be duplicated, and there's no global clock to coordinate timing. Understanding what makes a system distributed helps you recognize when you're facing distributed systems problems, not just concurrency issues.
Key Takeaway: A distributed system consists of multiple autonomous computers with separate memories that coordinate solely through message passing over a network.