You would be better off with the database server and php on the same server
- both sites.
You will find there is significant lag if there is a poor
connection between the web and database server, but if you are just
accessing web pages
and updating data, even with large pages there is not much delay.
You could always try both permutations and see, but that has been my
On 12/10/2007, Chris <[EMAIL PROTECTED]> wrote:
> 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
> > that is HEAVILY administered within the office with an administration
> > site (also PHP).
> > Problem: the office connection is having trouble keeping up with the
> > 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
> > 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
> > 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
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php