Ideas for scaling out database architecture
- by andrew
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