in reply to Hardware scalable web architecture

I'm still in the progress of making our company's app fully scalable. The only outstanding issue is the file server: I have yet to find a good solution to mirror our nfs server. Our data is in de low terabytes at the moment, and growing by a couple of gigabytes per day. A typical rsync run takes a couple of hours, so that's not a real-time solution. Does anyone have good pointers on this?

As for the rest, everything is redundant. We have 4 tiers:

  1. Static front-end Apaches
  2. mod_perl Apaches (*)
  3. Replicated MySQL servers
  4. A big fileserver
(*) Actually, this layer also has a number of Apaches setup to do straight cgi, for those long-running requests like file upload.

Here's some links I found useful in setting this up:

So that still leaves me with the file server. I haven't been able to investigate clustered filesystems such as GFS, Coda and others yet, but there may be a solution there.

And the other big thing I'm not trying to worry about just yet is how to mirror across data centers. I'll cross that bridge when we get there :)

Replies are listed 'Best First'.
Re^2: Hardware scalable web architecture
by wazoox (Prior) on Apr 10, 2006 at 14:46 UTC
    To secure your NFS servers, see for instance : http://linux-ha.org/HaNFS . It's pretty easy but using a SAN is mandatory. Of course, if you're building an HA system you're probably using serious RAID arrays, SAN and the likes anyway.
      Thanks for that link! I'm not sure whether it will work in our setup, but I'll look into it.

      We're currently using an AoE (ATA over Ethernet) device (made by Coraid). But I have to admit that I don't know much about this stuff: it was all set up by our ISP.

        It's probably perfectly OK with your AoE server, it's logically equivalent to a SAN. Keep us informed :)