I'm probably going to start with 3 webservers. 2 active, one passive. Only network load balancing using sticky sessions (based on IP). So once someone hits one webserver, they will be stuck to it until there is a problem. This would give me 3 copies of a catalog, one on each webserver.
I'm hosting on Windows 2003 Webserver edition. The database is on Windows 2003 Standard with SQL Server 2005. Based on what you said, my guess is, primarly because of performance, when doing lots of searching and heavy reads, it is best for the catalog to be local? So, I could have "read only" copies of the catalogs on each webserver, and a master copy on a "catalog" server. It would simply be a basic OpenBD installation and a small catalog "management" site (used to rebuild, cleanup, or delete catalogs). Every 10 minutes or so, the catalogs on the webservers would be sync'd to the master catalog. The way I have it now, everytime someone makes an update to their data and it's data that is kept in a catalog, the catalog is updated immediately. But I'm not sure how I would code it to update that remote catalog on another server.. Any ideas? -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
