Craig,
Thank you for your insight. Having never worked with clustering
solutions, what kinds of headaches might one see with that solution?
Does anyone know of any white papers that might shed some light into the
pros and cons of each solution?
-Erich-
Craig Huffstetler wrote:
I highly recommend you hire a consultant or a freelance DBA to try to work
this out.
You are talking about something pretty extensive. I would recommend
replication across quite a few high-end servers (all 64 bit of course with
plenty of RAM). Clustering can be a pretty big headache. A lot of this is
going to depend on what you see the most of (reads/writes? etc.). You are
correct in your thoughts, though, about having multiple database servers....
A project like this will most likely require much more initial information
and evaluations to find out a solution suitable to your needs.
On 10/22/07, Erich C. Beyrent <[EMAIL PROTECTED]> wrote:
A colleague and I are having a discussion about the best way to handle
high traffic sites. For example, take a social networking site with 1
million users.
I think it would be better to have multiple web servers with multiple
database servers in a master/slave scenario with replication.
My colleague supports the idea of clustering, with MySQL running on the
same box as the web server.
From a MySQL standpoint, are there any best practices for building high
traffic sites with a MySQL back end? Neither my colleague nor I are
DBA's, nor are we sys admin experts.
Any thoughts are most welcome.
-Erich-
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
