A system is fault tolerant if it keeps working when part of it breaks. The internet is fault tolerant for one reason: redundancy. Today you find a network’s weak spots — and price the fix.
No reading — this page is the reading. Yesterday’s string network is today’s whole lesson.
Internet. 6.6 showed traffic rerouting around a cut. Today that property gets its exam name — and its price tag.
The strings that matter most are the ones with no backup.
A system is fault tolerant if it can keep working when one or more of its parts fail. The internet is fault tolerant because of redundancy: there are extra paths, so when one fails, routing (6.6) uses another.
A single point of failure is a part whose failure alone cuts the network apart. A single path has nothing but single points of failure. A ring has none: break any one link and there’s still a way around.
The tradeoff. Redundancy isn’t free. Every extra link is equipment, installation, and upkeep for capacity you hope you’ll never need. Engineers choose how much fault tolerance a system is worth — a hospital pays for more than a backyard shed.
Pick a network. Click links to break them and see if every device can still reach every other. Then predict how many single points of failure it has — and check.
Five questions. For “how many connections must fail” items, find the device with the fewest connections first.
Cloud storage keeps copies of your files in several data centers. Airplanes carry backup systems. Your school’s grades are (hopefully) backed up. Every one of these is the same trade: pay for redundancy now, or risk losing everything when one piece fails.