How to Use This Guide

Welcome. A distributed system is just a group of computers that work together to look like one single service to the people using it. When you open a website, stream a video, or send a message, you are almost always talking to dozens or hundreds of machines pretending to be one. This guide explains, from the ground up, how those machines cooperate, why that cooperation is surprisingly hard, and what trade-offs engineers make to keep things working.

This guide is written for a complete beginner. You do not need a computer science degree, advanced math, or prior experience with servers. If you can picture a few people in different rooms trying to agree on something by passing notes under the door, you already have the right mental model for most of what follows.

The six sections are deliberately ordered so each one builds on the last:

• 1. What Is a Distributed System? — the vocabulary and the big picture. Start here even if you think you know it.
• 2. Why Distributed Systems Are Hard — the famous wrong assumptions ("fallacies") that trip everyone up, plus the difference between a fault and a failure.
• 3. Time, Clocks & the Ordering of Events — why you cannot trust the clock on the wall, and how "logical" clocks order events instead.
• 4. Vector Clocks & Causality — a smarter clock that can tell whether one event truly caused another, or whether two events just happened independently.
• 5. The CAP Theorem (and PACELC) — the single most quoted (and most misunderstood) rule about the trade-off between staying available and staying consistent when the network breaks.
• 6. Consistency Models — the menu of promises a system can make about how fresh and correct your data looks, from "always perfectly up to date" down to "it'll catch up eventually".

Sections 3 and 4 (clocks and causality) are the technical heart of the guide. Sections 5 and 6 (CAP and consistency models) lean on them — once you understand ordering and causality, the trade-offs in CAP and the ladder of consistency models stop feeling like jargon and start feeling like common sense.

Keep the Glossary open in another tab as you read — every bolded term in the sections is defined there in plain language. When you finish, the FAQ answers the questions most beginners ask next, and the Revision Cheat Sheet condenses everything onto one page you can glance at before an interview or an exam.