Books on writing distributed systems
aaron.trevena at gmail.com
Thu Mar 27 16:25:55 GMT 2008
On 27/03/2008, Paul LeoNerd Evans <leonerd at leonerd.org.uk> wrote:
> On Thu, Mar 27, 2008 at 12:44:35AM +0100, Dave Hodgkinson wrote:
> > Is this anything memcached can help with? If the data is read-mostly is
> > can shield the db from too many hits. And of course MySQL's replication
> > is way ahead of Postgres'.
> Would this be the replication that, for all databases run by a daemon,
> just writes the text of SQL queries into some journal file, that another
> process reads and streams across a network, to a third process on the
> other side, that replays them into its copy of the data with the mere
> hope that the same query will apply, and all will be well? That one that
> breaks for us about once a week... That replication?
I don't believe that mysql replication's expection is unreasonable,
you're replicating so the databases should be the same modulo what is
It's simple, recoverable, and relatively simple to troubleshoot. If
you read the documentation and follow it, it's also painless and
transparent to your databases - unlike postgres and sql server
replication in my experience.
We're using it for some reasonably large and busy databases, dozens of
concurrent updates, millions of records, hundreds of thousands of
users. No problems so far.
LAMP System Integration, Development and Hosting
More information about the london.pm