From owner-freebsd-isp Thu Oct 7 16:37:13 1999 Delivered-To: freebsd-isp@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id E4E4314BE5 for ; Thu, 7 Oct 1999 16:37:10 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (p1.telesto.eclipse.net.uk [212.104.138.193]) by proteus.eclipse.net.uk (Postfix) with ESMTP id 31DA49B23; Fri, 8 Oct 1999 00:37:09 +0100 (BST) Message-ID: <37FD275D.F30BFF9E@eclipse.net.uk> Date: Fri, 08 Oct 1999 00:06:05 +0100 From: Stuart Henderson X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en-GB,en MIME-Version: 1.0 To: Deepwell Internet Cc: freebsd-isp@FreeBSD.ORG Subject: Re: NetApp servers References: <4.2.0.58.19991007152026.02f2f9d0@mail1.dcomm.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can anyone point me to good documentation of building highly scalable web > servers or mail servers? I'd like to explore some different designs and > look at how they scale and increase reliability. > I noticed that Geocities offers all user pages at > www.geocities.com/~username. How do you suppose they are implementing > this? A large Sun box or two with NFS? Other alternatives would be to use squid or some natd-style code (or some custom hardware, perhaps some of the load balancing boxes can do this) and divert requests to the correct web server based on a hash of the username or database lookup. > >EarthLink do run mail on NetApps. They have a white paper somewhere on > >their website describing their setup (which involves some hacks in local > >delivery agents and POP3 daemons to work around the locking issue). One file per mailbox is not the only way to store mail :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message