Webfarms: The Only Way To Host!

Written by Brad Kingsley

Networks can be configured to be so incredibly redundant now - for reasonable prices - that there is no excuse for a data center not to achieve five nines (99.999%) of availability.

But what aboutrepparttar servers and applications? Why spend so much time up front configuringrepparttar 134343 network to make sure it doesn't fail, and then deploy an application to a single server?

Sure, there are ways to make sure individual servers have some redundancy to minimize failures -- things like RAID1, RAID5, or RAID10 (redundant array of inexpensive disks) which will protect against a disk drive failure (and I highly recommend this type of configuration for all production servers - and preferablyrepparttar 134344 use of hardware RAID vs. software RAID). But what happens if a file gets corrupt onrepparttar 134345 RAID array? Or a recent configuration change bringsrepparttar 134346 application down? Or a newly released patch conflicts with other settings and causes problems? Well, in these situationsrepparttar 134347 server will go down andrepparttar 134348 application(s) hosted on that server will be offline.

A good monitoring and alerting process will allowrepparttar 134349 system administrator to detect and address these issues quickly, but still there will be some level of downtime associated withrepparttar 134350 issue. And depending onrepparttar 134351 type of issue, evenrepparttar 134352 best system administrator might not be able to immediately resolverepparttar 134353 issue - it may take time. Time during which your application is unavailable and you may be losing business due torepparttar 134354 site interruption.

So, what can you do?

A great option - and one that has recently become more affordable - is to host your application on a webfarm. A webfarm consists of two or more web servers withrepparttar 134355 same configuration, and that serve uprepparttar 134356 same content. There are special switches and processes involved that allow each of these servers to respond to a request to a single location. For example, say we have two servers - svr1.orcsweb.com and svr2.orcsweb.com - that have 100%repparttar 134357 same configuration and content. We could configure a special switch* to handle traffic that is sent to www.orcsweb.com and redirectrepparttar 134358 traffic to either of these nodes depending on some routing logic. All clients visitingrepparttar 134359 main URL (in this case www.orcsweb.com) have no idea whether this is a single server - or ten servers! The balancing between nodes is seamless and transparent.

[*note: There is also software that could handlerepparttar 134360 routing process but experience and test have shown that these types of solutions are generally not as scalable, fast, or efficient asrepparttar 134361 hardware switch solutions]

The routing logic can be a number of different options - most common are:

Choosing the Right Host for Your Site

Written by Johnathan Brandon

When choosing a host for your website, there are both subjective and objective aspects to consider. Many ofrepparttar objective aspects are covered inrepparttar 134342 hundreds of articles that have already been written, but less often will you findrepparttar 134343 subjective aspects; those that are driven more by feelings and perception or your specialized needs.

There are many characteristics that you should generally expect all web hosts to include:

1. High Availability: Allrepparttar 134344 features inrepparttar 134345 world are worthless, if your site is not available when your visitors try to access it. This incorporates many different components. Do they use quality servers and hardware? Do they have multiple redundant connections torepparttar 134346 Internet? Do they have a lifecycle management program in place to ensure that you are not being hosted on a server built in 1987? (Most data centers plan for servers to have a 3 Ė 4 year lifecycle.)

2. Guarantee: Donít settle for them telling you that they haverepparttar 134347 best hardware and networks; ask them to back it up. Most hosts include a money-back guarantee of some sort. Given that it takes time to register or transfer domain names, develop your site, and upload it, make sure thatrepparttar 134348 host you choose offers you enough time to really evaluate their services. Thirty days is a pretty common guarantee. Be sure to testrepparttar 134349 speed of their support responses during this period (and during different hours ofrepparttar 134350 day), even if you donít need it immediately. You do not want to find out too late thatrepparttar 134351 host doesnít quite live up to your expectations.

3. Support: Your host should ideally offer support 24-hours/day. Some hosts offer this via e-mail or live chat, and others offer telephone support. Keep in mind that there is usually a financial trade off for different types of support, as they each involve different costs torepparttar 134352 host, which will inevitably be passed on. If you arerepparttar 134353 type of person, who needs to talk to someone onrepparttar 134354 phone to resolve an issue, make sure your host offers that as a support option, and be willing to pay a little more for it. Also, as stated in number two, be sure to test your host before your guarantee expires.

4. Growth: Make sure your host is growing. A host with low or negative growth numbers may be an indication that they are not attracting many new customers, or quite a few are leaving. There are some great search tools onrepparttar 134355 web, which will give you an idea of how many sites are pointing to various hosts servers. This should give you a starting point. But donít be afraid to ask also. It is very reasonable to expect that a host should takerepparttar 134356 time to answer your questions prior to you signing up with them.

Cont'd on page 2 ==>
ImproveHomeLife.com © 2005
Terms of Use