<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: digitalweb</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/digitalweb.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2007-10-05T23:29:32+00:00</updated><author><name>Simon Willison</name></author><entry><title>Client Side Load Balancing for Web 2.0 Applications</title><link href="https://simonwillison.net/2007/Oct/5/digital/#atom-tag" rel="alternate"/><published>2007-10-05T23:29:32+00:00</published><updated>2007-10-05T23:29:32+00:00</updated><id>https://simonwillison.net/2007/Oct/5/digital/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.digital-web.com/articles/client_side_load_balancing"&gt;Client Side Load Balancing for Web 2.0 Applications&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I recall that early versions of Netscape picked a random server from a hard-coded list each time a user clicked the “What’s New” button, back before server-side scaling techniques were well understood.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.sitepoint.com/blogs/2007/10/05/client-side-load-balancing-web-20-apps-is-voodoo/"&gt;SitePoint&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/digitalweb"&gt;digitalweb&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leizhu"&gt;leizhu&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/load-balancing"&gt;load-balancing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/netscape"&gt;netscape&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sitepoint"&gt;sitepoint&lt;/a&gt;&lt;/p&gt;



</summary><category term="digitalweb"/><category term="leizhu"/><category term="load-balancing"/><category term="netscape"/><category term="scaling"/><category term="sitepoint"/></entry></feed>