Query routing for replication?
Currently I have a single db running everything. This has become the bottleneck performance-wise. I know that with replication, I can have multiple nodes serve my _read_ requests, but the master must handle all _write_ requests.
To take full advantage of replication, do I need to modify my application logic and direct all write queries to the master and all reads to the slaves, or is there some kind of intelligent query router that will automagically send each request to the appropriate place?
Subject
Views
Written By
Posted
Query routing for replication?
2927
April 03, 2009 02:02PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.