In addition to what the others told you, security would be a big reason. If the application server is compromised, whether through
your application code or some other service on the box, then they also have local access to the database files.
If you setup a database server, you can open just the port(s) that are required to communicate with the database and allow only the
ip address of the application server. Yes, if the application server is compromised, it can be used to connect to database server,
but at least it's another hurdle.
Also, by splitting them, it allows much more flexibility, For instance, what if there is a problem with the application server or
you want to upgrade it? If everything is on one box, you would need to take the database down with everything else even though you
are not changing anything in the db.
----- Original Message -----
From: "Ratheesh K J" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Monday, August 28, 2006 12:49 AM
Subject: Seperating Application server and Database server
Hello all,
Currently our application and MySQL server are on the same machine.
When should these be seperated?
What are the main reasons that we should be having a seperate DB server?
Ratheesh Bhat K J
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
