Re: high availability

We mount our web farms' docroot as an NFS share. AFAIK, this is pretty common. Our performance is excellent. -jeremy brand http://www.JeremyBrand.com/Jeremy/Brand/Jeremy_Brand.html for more --------------------------------------------------------------------- We cannot do everything at once, but we can do something at once. -- Calvin Coolidge On Tue, 7 Nov 2000, alex wrote: > Date: Tue, 7 Nov 2000 18:52:32 -0300 > From: alex <alex@quad.com.ar> > To: michael@tapinternet.com > Cc: php-general@lists.php.net > Subject: Re: [PHP] high availability > > > I'd suggest putting things in a database. Not used coda directly, > > but we tried a similar approach under NT writing info to shared drives, > > and the performance wasn't as good as sharing info in a db. > > CODA may be vastly different, but SQL makes more sense, imo. > > Looks like I made a little confusion about this. I was thinking on using > CODA for 2 purposes: > 1. store ALL the php scripts (since all web servers will have to use the > same copy of them) > 2. store php data (like php sessions) > > I understand that the php data can actually be stored on SQL and might be > better as you mention, but any idea how reliable will be to use CODA for > storing the php scripts itself ? (so I dont have to rsync all servers and to > avoid having a master/slave relationship between them) > > > How large of a system do you anticipate this being? > > I actually don't know for sure. but what I do know is that we need something > scalable in case of success =) > > Thanks for your comments. > > Alex Verstraeten > Buenos Aires, > Argentina > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > >