Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would start here: <a href="http://en.wikipedia.org/wiki/Replication_(computer_science)" rel="nofollow noreferrer">wikipedia's replication article</a>, then read a couple of related papers on general replication techniques such as the replicated distributed state machine approach (<a href="http://research.microsoft.com/users/lamport/pubs/paxos-simple.pdf" rel="nofollow noreferrer">Paxos</a> (pdf)) and epidemic replication (<a href="http://research.microsoft.com/users/lamport/pubs/paxos-simple.pdf" rel="nofollow noreferrer">Google 'Epidemic Algorithms for Replicated Database Maintenance'</a>).</p> <p>For a practical overview, perhaps consider investigating the source code for Postgresql, which seems to have some replication technologies built in. <a href="http://www.pgcon.org/2007/schedule/events/20.en.html" rel="nofollow noreferrer">This presentation</a> purports to have some details.</p> <p>However, given that you're talking about deep analysis, the best approach is to make sure that you have a very sound understanding of fundamental distributed database systems issues. My copy of Date's <a href="http://rads.stackoverflow.com/amzn/click/0321197844" rel="nofollow noreferrer">Introduction to Database Systems</a> has a few pages on distributed databases and their attendant issues. I should think a textbook dedicated to distributed databases would have much more detail - <a href="http://rads.stackoverflow.com/amzn/click/0136597076" rel="nofollow noreferrer">this one</a>, for example, looks promising. </p> <p>You can go much deeper if you read Ken Birman's work on Virtual Synchrony, and most things that Leslie Lamport has ever written. These will attack the problem from the perspective of a general distributed systems approach.</p> <p>Good luck!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload