On 10/13/06, <b class="gmail_sendername">Kevin Burton</b> <<a href="mailto:burton@tailrank.com">burton@tailrank.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We really suffer from MySQL replication scalability issues. Basically you can scale reads but not writes.......<br clear="all"><br>I'm
thinking of migrating some portions of our app to MySQL cluster because
basically it's an all memory DB and (in theory) should scale linearly
if we need to index more data.
</blockquote></div><br>
It's not going scale linearly in practice exactly because you're going
to have writes and communication overhead between the nodes. With a
memcached backend, you'll get much closer to actual linear scalability
because there is no internal communication necessary.<br>
<br>
I would be looking more for the advantage of failover/reliability in
clustering the DB backend and use memcached for the actual scalability.<br>
<br>
Regards,<br>
<br>
Serhat<br>