The book’s last scene is a circular wait — each waiting for the other to move — and neither party gets out of it.
Why this matters
Each of them waits for the other to go first, which is Part II’s subject arriving as the closing joke. Notice that the polite version has no rule for ending — one of them gives in and it changes nothing, because what actually holds them there was never the argument about who goes first.The distributed arc — and the book — close the way everything else did: the professor, the student, and one last look back.
Everything the distributed arc earned, gathered in one place — click each row for where it was learned:
| the belief | |
|---|---|
| 1 | Everything can fail |
| 2 | Redundancy hides failure |
| 3 | Retry is a workhorse |
| 4 | Communication is the heart |
| 5 | Protocols shape everything |
| 6 | Two ways to build a distributed FS |
The End — Three Easy Pieces
And that’s the book. We virtualized one CPU into many and one memory into many address spaces; we made threads cooperate without stepping on each other; we made data persist across crashes, failing disks, and lying devices — and finally stretched it across a network of machines that fail all the time. Virtualization, concurrency, persistence: the three easy pieces. Thanks for reading — now go build something.If you remember only three things
-
A protocol with no termination rule is the last thing the book demonstrates. The student has just declared that the exact exchange between two parties decides everything, and then walks straight into an exchange that cannot end.
-
Neither of them knows whether the book is over. Asked directly, the professor is not sure and says nobody tells them anything — the character who has explained everything else has no information about the one thing the reader can see plainly.
-
Neither of them can leave. Told to go first, the student finds that taking part in these conversations is the only thing they know how to do, and the professor admits to being in exactly the same position.
Check yourself: the distributed arc in review
1.The student's headline lesson about distributed systems is a pair of ideas. What are they?
2.Which 'basic technique' does the student single out as really useful?
3.Why does the student conclude that protocols matter enormously?
4.The arc showed two contrasting ways to build a distributed file system. Which pairing is right?