A Note on Free Web Hosting

Written by J. Ratliff

There are literally thousands of places to get Free web hosting. Maybe you already have one. Are you happy with it? Do you wish you could do away withrepparttar advertising you must put up with?

There a number of reasons why you should not use free web hosting. If you only have a personal website for friends or family, than a free website is fine. However, if you are trying to sell a product or attract people to your website, it is a bad idea. Here is why.

1. Free Websites have no guarantee. They may be here today gone tomorrow.

2. Free websites usually put ads on their website, making your website look like an advertising medium for who knows what product.

Webfarms II: Balancing The Load.

Written by Brad Kingsley

Okay, so you understand webfarms now. What'srepparttar magic that actually distributesrepparttar 134344 load, and how does it determine howrepparttar 134345 distribution is handled?

At ORCS Web we userepparttar 134346 Foundry Server Iron products to perform our webfarm load-balancing. If one of them fails,repparttar 134347 other instantly takes over (In our testing, it had sub-second fail-over!)

So what is this "Server Iron" thing? In simplest terms, it's a layer 4-7 switch. It has multiple network ports on it and can be used literally like other types of switches. But, it can also load-balancing and traffic distribution. A VIP (virtual IP) can be assigned torepparttar 134348 SI (Server Iron) and it then handles all traffic sent to that address/VIP. Further configuration is done to tellrepparttar 134349 SI what to actually do withrepparttar 134350 traffic sent torepparttar 134351 VIP address.

The traffic that hitsrepparttar 134352 VIP onrepparttar 134353 Server Iron is of course redistributed to a number of server nodes sorepparttar 134354 client request can be satisfied - that'srepparttar 134355 whole point of a webfarm. If one or more server nodes are not responding,repparttar 134356 switches are able to detect this and send all new requests to servers that are still online - makingrepparttar 134357 failure of a server node almost transparent torepparttar 134358 client.

The traffic can be distributed based on a couple different logic algorithms. The most common are:

* Round Robin: The switches send requests to each server in rotation, regardless of how many connections each server has or how fast it may reply.

* Fastest response: The switches selectrepparttar 134359 server node withrepparttar 134360 fastest response time and sends new connection requests to that server.

* Least connections: The switches send traffic to whichever server node shows as havingrepparttar 134361 fewest active connections.

* Active-passive: This is called Local/Remote on a Foundry switch, but is still basically active/passive. This allows one or more servers to be designated as "local" which marks them as primary for all traffic. This is combined with another method above to determine what orderrepparttar 134362 "local" server nodes have requests sent to them. If a situation were to arise that allrepparttar 134363 "local" (active) server nodes were down, then traffic would be sent torepparttar 134364 "remote" server nodes. Note that "remote" in this case doesn't really have to mean remote -repparttar 134365 "remote" server could be sitting right next torepparttar 134366 "local" servers but it is marked as remote inrepparttar 134367 configuration to let it operate as a hot-standby server. This setting can also be used in a true remote situation where there are servers in a different physical data center - perhaps for extreme disaster recovery situations.

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