One Web Site, Multiple Sub-Domains

They have: 6 posts

Joined: May 1999

This is a question for the saviest of web masters. I have a client who decided, for one reason or another, to split one large web site into many sub-domains, (micro web sites).
For example, the main site is called http://www.main_campus.com. They then created sub-domains like class1.main_campus.com, class2.main_campus.com, class3.main_campus.com, etc... There are about 50 of these.

They are running an in-house UNIX server.

Will someone please explain any advantages of breaking a large web site apart in this way.

It was a nightmare to code, link and troubleshoot. We were not given access to the actual server space and were forced to create a matching development area on our own servers.

We did it by using traditional sub-directories and then converting all the links to absolutes prior to shipping.

My question again is why would someone want to choose sub-domains over the traditional sub-directories.

Thank you in advance for your responses.

Robert

Brian Farkas's picture

They have: 1,015 posts

Joined: Apr 1999

Really, I have a feeling it's personal preference. The most likely reason, of course, is simply for navigation purposes- it's much easier to navigate a smaller site than a larger one (usually), and they probably feel that splitting the site up into subdomains will be more effective at separating the sites than doing the same with subdirectories.

They have: 60 posts

Joined: Aug 2000

I think because it's cooler, easier for their visitors to remember!

Justin S's picture

They have: 2,076 posts

Joined: Jun 1999

Yeah, I agree, it's mostly a personal preference. They're also easier to remember. For instance, I always type 'movies.yahoo.com' into my browser when I'm searching for a movie to see. It might not be much easier then 'yahoo.com/movies,' but for me personally it's much easier.

They have: 453 posts

Joined: Jan 1999

Just a few reasons why to split up a big site.
- load balancing is much easier/cheaper
- accounting is easier
- the system is more stable (eg. if one site goes "crazy" the rest need not be affected)
- security, if it's on a different host you need to recrack that one too
- inhouse responsibility can be split up

In short,
for very large sites it's easier to keep the thing up and running.
There are transparent balancing solutions, but these require a fast internal replication system ...

just my 2p

anti

Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.