Editing Distributed Systems (section)

== <span style="color: #FFFFFF;">Understanding</span> ==
Distributed systems are understood through '''Coordination''' and '''Trade-offs'''.

'''1. The CAP Theorem (The "Choose Two" Rule)''':
This is the most important law in distributed systems.
* '''Consistency (C)''': Every node sees the same data at the same time.
* '''Availability (A)''': Every request gets a response.
* '''Partition Tolerance (P)''': The system keeps working even if the network between nodes breaks.
* Because the network *always* breaks eventually (P), you have to choose between **C** and **A**. Do you want the answer to be "Perfectly Correct" (C) or "Fast and Always There" (A)?

'''2. Horizontal vs. Vertical Scaling''':
* '''Vertical (Scale Up)''': Buying a "Bigger" computer. (Expensive and has a limit).
* '''Horizontal (Scale Out)''': Buying "More" cheap computers. (This is how modern systems like Google and AWS work).

'''3. The Fallacies of Distributed Computing''':
New developers often make dangerous assumptions that cause systems to fail:
* They assume the network is "Always Reliable."
* They assume "Latency is Zero."
* They assume "Bandwidth is Infinite."
* In a distributed system, you must "Design for Failure." You assume everything will break and build the software to handle it.

'''Eventual Consistency''': A compromise used by systems like Amazon or Facebook. If you update your profile, your friend in Australia might not see it for 1 second. The data is "Eventually" consistent, allowing the system to stay incredibly fast.
</div>

<div style="background-color: #8B0000; color: #FFFFFF; padding: 20px; border-radius: 8px; margin-bottom: 15px;">