On 8/22/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> I am now at the prospect of using a MySQL database in the form of a
> 2-machine master-slave cluster. If I understand things right this
> requires Django to actually know which queries should be directed to
> which host, i.e. writes on
sqlrelay router might be of use:
http://sqlrelay.sourceforge.net/sqlrelay/router.html
On 8/22/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
>
> Alexis Smirnov wrote:
> > If the goal is scalability, one needs to assume a cache-based solution
> > isn't appropriate or isn't enough, right?
>
> Yes,
Alexis Smirnov wrote:
> If the goal is scalability, one needs to assume a cache-based solution
> isn't appropriate or isn't enough, right?
Yes, we need scalability. We are expecting couple of tens of millions
request a day in a near future.
As for cache... I didn't evaluate it in practice but
If your primary goal is redundancy (not scalability) then you could
maybe get away with using the master for all queries while keeping the
slave as a "hot spare".
We've been using this master-slave configuration with a django-based
app. All queries (read and write) go to the master. When master
Hi!
I am now at the prospect of using a MySQL database in the form of a
2-machine master-slave cluster. If I understand things right this
requires Django to actually know which queries should be directed to
which host, i.e. writes on master, reads on both master and slave.
I'm about to start
