We implement this scenario and I don't see any significant delay issues. The LB does create a single point of failure, but you're always welcome to buy a second LB and set it up in failover/distributed mode. Having said that, loadbalancers usually don't windows, and as a result tend to be a little more stable.
RUss > -----Original Message----- > From: Brad Wood [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 27, 2007 11:07 AM > To: CF-Talk > Subject: RE: Targetting an instance > > Q: Is there a sigificant performance impact proxying all web traffic > through a HW LB twice for each page hit? > > What also concerns me is the single point of failure our load balancer > creates for us if IT was to go down. I don't know if there is an easy > way around that though. > > ~Brad > > -----Original Message----- > From: Robertson-Ravo, Neil (RX) > [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 27, 2007 3:06 AM > To: CF-Talk > Subject: Re: Targetting an instance > > I would seperate the layers with H/W LB sitting in front and balancing > load > to the web servers, who in turn point to another H/W LB (maybe the same > one) > who hands off the requests to the Application Layer while JRun handles > the > session rep. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273859 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
