<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Problems in Loadblancing</title>
	<atom:link href="http://www.royans.net/rant/2000/12/03/problems-in-loadblancing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.royans.net/rant/2000/12/03/problems-in-loadblancing/</link>
	<description>@royans.net</description>
	<pubDate>Tue, 06 Jan 2009 20:46:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: loadbalancer</title>
		<link>http://www.royans.net/rant/2000/12/03/problems-in-loadblancing/#comment-1006</link>
		<dc:creator>loadbalancer</dc:creator>
		<pubDate>Tue, 01 Aug 2006 13:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.royans.net/logs/2000/12/03/problems-in-loadblancing/#comment-1006</guid>
		<description>It always amazes me how poorly designed certain so called 'enterprise applications' actually are. Every blue print for enterprise applications I have ever seen has definitively stated that the application layer must preserve it's own state.

You won't catch Google/Msn/Slashdot or any other high performance web site using something as privative as a load balancer for preserving state. Persistence will be built into the application from the ground up taking into account all the performance issues surrounding that and dealing with them.

It is a trivial task to implement persistence for web applications on any platform apache or IIS (using a combination of URL/Cookie/Database). 

When you need to scale you just stick a fast pair of layer 4 load balancers on the front of the farm and grow. It really shouldn't matter what IP address people are coming from and on a properly designed site it never will.</description>
		<content:encoded><![CDATA[<p>It always amazes me how poorly designed certain so called &#8216;enterprise applications&#8217; actually are. Every blue print for enterprise applications I have ever seen has definitively stated that the application layer must preserve it&#8217;s own state.</p>
<p>You won&#8217;t catch Google/Msn/Slashdot or any other high performance web site using something as privative as a load balancer for preserving state. Persistence will be built into the application from the ground up taking into account all the performance issues surrounding that and dealing with them.</p>
<p>It is a trivial task to implement persistence for web applications on any platform apache or IIS (using a combination of URL/Cookie/Database). </p>
<p>When you need to scale you just stick a fast pair of layer 4 load balancers on the front of the farm and grow. It really shouldn&#8217;t matter what IP address people are coming from and on a properly designed site it never will.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
