Make it survive

What happens when many machines, many copies and many failures meet.

1. 1Data MovementHow do records cross between two systems that have independent rates, independent availability and independent lifetimes, and what are you willing to lose when the assumption underneath the crossing breaks?
2. 2Distributed Systems CoordinationWho is allowed to decide, and how does everyone else learn the decision without asking?
3. 3Transactions & Concurrency ControlWhat happens when many users change the same data at the same time, and how do we keep the result correct?
4. 4Consistency & Isolation ModelsWhen many users, many objects and many copies exist at once, which histories does the system promise never to show, and who writes the code for the histories it does show?
5. 5Fault Tolerance & Delivery SemanticsWhat is the cheapest thing that can be safely done twice?
6. 6Emergent Failure DynamicsWhat happens when nothing is broken, every component is healthy, and the system's own response to stress makes the stress worse?
7. 7Scheduling & Workload ManagementWhich work runs now, which work waits, and who pays for the waiting?

Next route: Make it cheaper →