Ideas for scaling out database architecture

Posted by andrew on Server Fault See other posts from Server Fault or by andrew
Published on 2010-04-01T15:40:08Z Indexed on 2010/04/01 15:43 UTC
Read the original article Hit count: 470

We're looking to scale out our existing database architecture and need some advice on which way to go.

We currently have 2 web servers behind a load balancer that both read & write to a single master database which replicates to a slave.

Ideally, I'd like each of the webservers to point to their own master DB and have the data between the 2 synchronised but from what I've read, using any kind of master-master or ring-replication is discouraged.

I'm looking for a general "what do other people do" kind of answer - database vendor isn't a concern at the moment but we'd like to stay with MySQL or convert to MSSQL.

Any ideas would be gratefully received.

Many thanks,

Andrew

© Server Fault or respective owner

Related posts about replication

Related posts about scaling