iRule for splitting SQL Write and Read

One thing that makes this a hard issue is that your parser in the iRule needs to understand something of the SQL statement. For example, if you simply send the SELECTS to one pool and the UPDATE, INSERT and DELETE to another pool, you also have to handle UPDATE . Not a very common construct, but still to be handled. I hate to say it but setting up an MYSQL cluster might be a more robust solution.

 

 

Tom Schaefer SET column=something where id in (SELECT id from