Home » Performance » MySQL » Mysql replication read / write splitting: Mysql proxy or in software?
Mysql replication read / write splitting: Mysql proxy or in software? [message #3641] Mon, 20 October 2008 18:08 Go to previous message
al.james  is currently offline al.james
Messages: 16
Registered: October 2006
Junior Member
Hi there...

I am rolling out a web app from a single server to a cluster using mysql replication. Obviously, I need to allow for read / write splitting to send write queries to the server.

The way I see it there are two options:

1) Use mysql proxy to do this.
2) Handle it in software. Rewrite the DB abstraction layer to separate read queries from write queries. Connect in a lazy manner, i.e. only connect to the master when (if) a write arrives.

2 is not that hard due to the way the DB abstraction is handled, however, using mysql proxy would side step this coding (and therefore code maintenance) nicely.

Not having used mysql proxy, I done know how stable it is and if it would slow things down.

Would mysql proxy sidestep this problem nicely, or would it introduce 'another component to go wrong' in my system. Does it introduce performance lags / increase resources used?

Read Message
Read Message
Previous Topic:Limits and datatype for connection_id()
Next Topic:Advice
Goto Forum:

  


Current Time: Mon Jul 6 21:36:58 EDT 2009

Total time taken to generate the page: 0.01000 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 2.7.7.
Copyright ©2001-2007 FUD Forum Bulletin Board Software

MySQL is a trademark of Sun Microsystems.
InnoDB is a trademark of Oracle Corp.

Percona Performance Forums are a service of Percona, Inc.
Not affiliated with Sun Microsystems or Oracle Corp.