Hi Götz, On Dienstag, 9. Dezember 2008, Götz Reinicke wrote: | My question is, what do you think about using e.g. one server as | webserver, the other as mysql server ... so the database traffic will go | across the network. So that I have only one service running on one | server and not like now the webserver bundled with the database. | | The most obvious advantage from my point of view: I only have one mysql | server to manage and not three or four. (Likewise the webserver) | | The disadvantage would be the delay accross the network I think.
As Steve already pointed out, network performace shouldn't be an issue if you have GigE connectivity; we also do it now for years without a problem. The biggest issue I see is that you probably create another SPOF here. What if the webserver is up running but the database server dies for some reason? I'd strongly suggest to set up database replication including a failover solution (e.g. heartbeat). You could in general do something similar with your webserver and other systems. Ciao, Thomas -- Thomas Pundt <[EMAIL PROTECTED]> ---- http://rp-online.de/ ---- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
