List:General Discussion« Previous MessageNext Message »
From:Aodhan Cullen Date:June 28 2003 11:33am
Subject:Re: distributed database architecture for a large database
View as plain text  
6/27/03 6:37:49 PM, Jeremy Zawodny <Jeremy@stripped> wrote:

>> My read/update ratio would be something along the lines of 1:3, 3
>> updates for every read. So it is highly unusual, and more or less
>> rules replication out of the picture.
>
>I'm unclear why you can't use replication for this.  There must be an
>assumption about what you're doing that we do not share.
>
>If you read from the slave and write to the master, why does this not
>work?

A slave would simply not be able to keep up, replication works really well if 
you have a lot of reads, and a small number of updates. This is reverse ways, 
and needs a different approach.


Thread
distributed database architecture for a large databaseAodhan Cullen26 Jun
  • Re: distributed database architecture for a large databaseJoseph Bueno27 Jun
    • Re: distributed database architecture for a large databaseJoseph Bueno27 Jun
      • Re: distributed database architecture for a large databaseAodhan Cullen27 Jun
  • Re: distributed database architecture for a large databaseBrent Baisley27 Jun
    • Re: distributed database architecture for a large databaseAodhan Cullen27 Jun
  • Re: distributed database architecture for a large databaseJeremy Zawodny27 Jun
    • Re: distributed database architecture for a large databaseAodhan Cullen28 Jun
      • Re: distributed database architecture for a large databaseGuy Davis4 Jul