<?xml version="1.0" encoding="UTF-8"?><item><title>Joel on Load Balancing</title><description>&lt;P&gt;I'm commenting on &lt;A href="http://genehack.org/computers/software/joel-on-crack.html"&gt;a comment by John Stephen Jacobs Anderson&lt;/A&gt; (who seems to have too many names) on &lt;A href="http://www.joelonsoftware.com/items/2005/06/15.html"&gt;a comment by Joel&lt;/A&gt; (who could use another) on load balancing.&amp;nbsp; &lt;/P&gt;&#13;
&lt;P&gt;Basically, Joel said that letting Windows take care of load balancing is better than using a hardware load balancer, because if your load balancer goes down, you're offline.&amp;nbsp; I would tend to agree.&amp;nbsp; John said that that's baloney, because if you have a load balancer, you have two of them.&lt;/P&gt;&#13;
&lt;P&gt;But for a small shop, two load balancers is expensive, and doesn't actually add any benefit over letting Windows do it.&lt;/P&gt;&#13;
&lt;P&gt;ASP.NET gives you &lt;A href="http://www.eggheadcafe.com/articles/20021016.asp"&gt;various ways to manage session state&lt;/A&gt;, including serializing state into the database, so even if one of your machines goes down, a client in the middle of something that requires server side state doesn't lose anything.&lt;/P&gt;&#13;
&lt;P&gt;Doing the load balancing is a little more work for the servers, but peanuts in the grand scheme of things.&amp;nbsp; Joel's got a system that works, and saved himself the $$ of two hardware load balancers.&amp;nbsp; Makes sense to me.&lt;/P&gt;&#13;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description><pubDate>Thu, 01 Sep 2005 19:17:09 GMT</pubDate></item>