Distributed Revision Control
Distributed revision control systems (DRCS) take a peer-to-peer approach, as opposed to the client-server approach of centralized systems. Rather than a single, central repository on which clients synchronize, each peer's working copy of the codebase is a bona-fide repository. Distributed revision control conducts synchronization by exchanging patches (change-sets) from peer to peer. This results in some important differences from a centralized system:
- No canonical, reference copy of the codebase exists by default; only working copies.
- Common operations (such as commits, viewing history, and reverting changes) are fast, because there is no need to communicate with a central server.
Rather, communication is only necessary when pushing or pulling changes to or from other peers.
- Each working copy effectively functions as a remote backup of the codebase and of its change-history, providing inherent protection against data loss.
Read more about this topic: Revision Control
Famous quotes containing the words distributed and/or control:
“Taking food alone tends to make one hard and coarse. Those accustomed to it must lead a Spartan life if they are not to go downhill. Hermits have observed, if for only this reason, a frugal diet. For it is only in company that eating is done justice; food must be divided and distributed if it is to be well received.”
—Walter Benjamin (1892–1940)
““Have we any control over being born?,” my friend asked in despair. “No, the job is done for us while we’re sleeping, so to speak, and when we wake up everything is all set. We merely appear, like an ornate celebrity wheeled out in a wheelchair.” “I don’t remember,” my friend claimed. “No need to,” I said: “what need have us free-loaders for any special alertness? We’re done for.””
—Marvin Cohen, U.S. author and humorist. The Self-Devoted Friend, New Directions (1967)