Re: Remote DB Connection: Pros and Cons?
| From: | Chris | Date: | Fri, 12 Oct 2007 00:01:19 +0000 |
| Subject: | Re: Remote DB Connection: Pros and Cons? | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-44192@lists.php.net to get a copy of this message | ||
Tony Grimes wrote:
Have any of you tried running a PHP website using a remote database connection? We currently have an in-house PHP website driven by a PostgreSQL database that is HEAVILY administered within the office with an administration sister site (also PHP). Problem: the office connection is having trouble keeping up with the website traffic. Our IT guys want to outsource the whole server to a co-location facility, but the administrators don't want the extra lag on the admin site. Is it feasible to host the database and admin site in the office, but outsource the website and connect to the office database remotely? Is there any other way to do this?Do the website and admin area reference the same database tables? If they don't, split the database up and keep the website db on the website server and the other internally. If they do, which one is the 'primary' set? ie which one gets updated? You could use replication to keep them in sync (http://www.slony.info/ for example). -- Postgresql & php tutorials http://www.designmagick.com/