Web Hosting Tips and Advice

Free Domain Name Registration and Web Hosting

2008-09-11T00:30:00.000-07:00

Domain names are another piece of the puzzle when it comes to starting a website. Many hosting companies offer a free domain name with the purchase of one of their hosting plans. But we recommend registering your domain name elsewhere. Domain name registration services are fairly inexpensive (usually about $10 a year) so you really aren't going to save a whole lot by taking advantage of the free domain name. The problem is that when you register your domain name through the hosting company, they can use this as leverage if you ever decide to cancel. Even if your web host does handle it in a professional manner, you will need to contact their customer support in order the transfer the domain name. This will be a hassle.
We recommend using actual domain name registration services when registering domain names. GoDaddy is one of our top picks because it is one of the top cheap domain name registration services. With GoDaddy, you will be given an account where you can manage all your domain names. From within this account, you can easily set your nameservers (a nameserver is the number you type in that tells the domain registrar where to host your domain) without having to jump through any hoops. This means you can cancel your old host and get a new one at any time. All you will need to do is log into your GoDaddy account and set the nameservers to the new host.
By using a domain registrar like GoDaddy, you're in control of your entire web business!

What is cPanel?

2008-09-11T00:29:00.000-07:00

cPanel is a control panel that allows you to manage your website through the web. When you sign up for a hosting account with a hosting provider that uses cPanel, you will receive your cpanel address and a login and password to access it. Most of the time, you can access your cpanel account by typing in your domain name, then /cpanel. For example, www.domainname.com/cpanel. From that page, you will be prompted for your user ID and password.
Please keep in mind that this will not work until you have your domain name set up to point to your hosts nameservers. Your host will usually provide you with another web address for reaching your c panel while you are waiting for the domain name to propagate (basically a fancy way of saying point to the right host).
From within c panel you can do all sorts of things like set up your email accounts, backup your website files, FTP files to your hosting account and even view your web traffic statistics. If you are planning on installing scripts of any sort to your site, you will likely need to log into cPanel (or let a programmer access your cPanel account for you).
cPanel often comes with fantastico which will enable you to set up a content management system (and many other popular componenets) for free with just a few clicks. This is a huge timesaver as any script in fantastico can be installed without needing any advanced knowledge of setting up scripts.
So learn cPanel and your web building and hosting set-up will be much easier.

How to Choose a Domain Name

2008-09-11T00:28:00.000-07:00

Deciding on a domain name can be tricky. First you need to come up with something representative to your website and second, it needs to be available.
If someone already has your domain name, you will either have to try to buy it from them or choose again. Therefore, we recommend that you come up with a few names before ever checking the availability.
This way you have a few backups.
At this point, getting a .com name is still important if you want consumers to remember your website. Most people will have trouble enough remembering the name so you don't need to make it more complicated by changing the ending from .com to .net (or something else). So if branding is even a little part of your overall strategy, you'll want a .com ending. If you are building your website for your personal use then you may still consider .com as it is very unlikely your friends and family will remember anything else. The .com ending has been branded tremendously!
Another factor to consider when selecting a domain name is whether you want to go with the unique factor or the keyword factor. An example of what I consider the unique factor is Amazon.com. The name really doesn't correlate to what their selling. It's just a brand. Names like this tend to stick rather well. If you want to use the unique factor when selecting your domain name be sure to keep it easy to spell and under a few syllables (4 or less is good). Other examples of popular domain names with the unique factor include; youtube.com, yahoo.com, google.com, zillo.com, and ebay.com. Depending on what your plans are for your site,adding in the unique factor may or may not be important to you.
The other factor to consider is what I'll call the keyword factor. The keyword factor simply means figuring out what your site will be about and getting the keyword in the domain name. For example, realtor.com. People looking for the site might type the keyword realtor into the search engines. Having the word realtor in the domain name (in this example it's the whole name), is helpful for getting the site ranked high for that keyword. The site you are currently on, Top-5-Web-Hosting-Charts.com is another example of the keyword factor as we've used the words web hosting in our domain name.
Once you have a list of potential domain names, you will want to check their availability. GoDaddy is a great domain name registrar that will allow you to check the availability of domain names before you buy. If the domain name you wanted was already taken, GoDaddy will also present you with a list of alternatives that are available. From your list of available domain names, you should narrow it down to the final contender and get it registered right away. It is possible someone else will take it if you think for too long!

Web Hosting Reviews To Help You Save Your Time & Money

2008-09-11T00:27:00.000-07:00

Top 5 Web Hosting Charts was established to help you find the best web hosting for your needs. We make it our job to find and rate the top web hosts on the net and use this site to present our web hosting ratings to you. There are a number of web hosting companies out there that have horrible customer support and are difficult to work with.
Unfortunately, these same web hosting companies know that they can still bring in the clients by offering high affiliate commissions. That means third party web sites will still rank their web hosting services as high even when they really aren't.
We don't operate that way.
Instead, we strive to find the best web hosting services and rate them based on our own experiences. We also review web hosting forums to determine how other clients feel about each particular host. You can rest assured that any web hosting company that doesn't provide the highest quality web hosting service and customer support will never make our Top 5 Web Hosting Charts.
We are currently recommending the following hosts (click on each to read the full review):
Bluehost.com
Lunarpages
midPhase
Hostrocket
Hostgator
You may also review our at a glance best web hosting chart.
How Do We Conduct Our Web Hosting Reviews?
The hosts are rated based on reliability, value, and customer support.
The best web hosting companies must have a 99% or higher uptime. The last thing you want is to go to the trouble of setting up your site and driving traffic to it only to experience lots of downtime. While no host can be perfect, reliability is a major factor. When we first started out, we had the misfortune of choosing a popular web host that was down at least 5 hours every week (obviously, they aren't recommended here).
Customer Service is also a very important factor. Even if you know what you are doing, you will likely have problems or questions. The top hosts have superior customer service support which include a number of methods for contacting them and friendly, professional support.
Both reliability and customer service are rated based on our own experiences with these hosts as well as the reviews of others.
Value is an easy one to gauge. Value is based on the web hosting package offered such as; storage space, bandwidth and number of domains that can be hosted on an account. We also take into account the extra features like the webhosting control panel available.
All of the web hosting services that make it to our top 5 chart are quick to set up your hosting account. We look for hosts that can set up your account within 24 hours or less.
At the top of each web hosting review, you will see a chart that shows the hosts rating based on value, features, storage space, bandwidth, and customer service. Each of these will be rated from 1 to 5 (with 5 being the highest). Under the chart, we provide you with a total score which is the rating the host received divided by the total score (currently 30). We show you this score as a percent. The absolute best hosts on our list will have a score of 90% or above.
It can be difficult to score hosts with such detail (because factors change all the time). Therefore, all of the hosts on our top 5 web host chart get our seal of approval. You may want to investigate them and decide which one to use based on your needs.

Unix vs Windows-Based Hosting, Which Is Better?

2008-09-09T23:45:00.001-07:00

An operating system functions largely out of sight, or at least is supposed to. It doesn't matter to non-geeks how a file gets stored, or how memory is used, or how simultaneous processes share the limited resources available on a computer. These are among the basic functions of any operating system. Yet, you can find very passionate supporters - who offer very detailed lists of pros and cons - for every operating system. Why? Because, though the low-level functions of an operating system do their work out of sight, there are many other features that rise to visibility. Sometimes, they do so when they're not supposed to. Weighing the pros and cons objectively could consume a book. But to select a web host operating system, a manageable level of considerations apply. They can be weighed even by those who don't know a processor queue from a pool cue. Learning Curves For most web site owners, administering the site/server is just overhead. It's not something they take pleasure in doing and they have plenty of other things to worry about. Many wouldn't know how and have no interest in learning (rightly so, given their priorities). Consequently, ease of administration is paramount for such people. Whether a Unix-based site (usually Linux these days) is easier to administer than Windows depends on your current skill set and the type of tools and level of access the web hosting company provides. But in general Linux is more difficult to install and maintain than Windows and the learning curve is steeper. FTP and Control Panels Often, you don't have to care. For many, the operating system is fairly transparent. FTP file transfers to get a new web page up to a Windows server are very much like they are to a Linux-based site. The user/administrator simply doesn't see what's behind the curtain. Many companies provide other utilities that completely mask any awareness of the operating system underneath. When that's the case, the web site owner has no reason to care, until or unless they need or want to go 'inside the black box'. Performance Performance issues can be relevant in selecting which operating system host type to choose. But for the most part, that aspect is outside the web site owner's control. Overall performance can be good or bad on either system, depending on many factors that the publisher will rarely see. The issue is a wash, as far as tipping the scales is concerned. What is more likely to be seen by a web site owner, at some point in their (and their site's) development is the database product that can be used to store information. Databases Microsoft SQL Server is relatively simple to use, yet extremely powerful and can deliver great performance. But it doesn't run on Linux. At least, not without special software to emulate Windows, which usually kills performance. On the other hand, with a bit of time invested, MySQL isn't significantly more difficult to learn than MS SQL Server and there are many free installations. Cost may well outweigh other considerations for most on this issue. Programming Languages Last, but not least, there are differences in programming languages that can be (or at least typically are) used on Windows vs Unix. If you have programmers who are skilled in Visual Basic, ASP and other Microsoft technologies, then a Windows-based host will be your preferred choice. For Perl and PHP programmers, Linux is the more common platform of choice. No single factor can push you to one versus the other operating system. And, in the long run, it isn't the primary consideration, unless you just enjoy playing with operating systems.

The Internet and How It Works

2008-09-09T23:44:00.002-07:00

In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.

Sharing A Server – Things To Think About

2008-09-09T23:44:00.001-07:00

You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact.

Redundancy and Failover

2008-09-09T23:43:00.000-07:00

Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Managing Disk Space

2008-09-09T23:42:00.001-07:00

Few things are less exciting than managing the disk space that always seems to be in too short a supply. But few things are more important to the health and well being of your site. The most obvious aspect of managing disk space is the need to have enough. If you have only a few dozen web pages, that's not an issue. But as the amount of information (web pages, database content and more) grows, the quantity of free space goes down. That's important for two reasons. All permanent information on a computer is stored on hard drives. Temporary information is often stored in memory only. The two components are completely separate, though they are sometimes confused with one another. As the amount of free space on the hard drive decreases several effects occur. Here's one way to picture them... Imagine you had a table with a certain area and you lay out playing cards on the table. At first, you lay them out in order, the 2 at the side of the 3, then 4, and so on. But then you pick up one or two cards from the middle and discard them. Then you add some more cards. Pretty soon things look pretty random. Now cover the cards with a big opaque sheet of paper. You want the cards to appear in order when displayed to someone. A special robot could be designed to always pick up the cards from underneath the sheet in order. Or, it could slide a hole in the sheet over the cards to display them in the correct order (2, 3, 4, ...), no matter what order they are really in. That's similar to how the operating system always shows you information in a sensible way, even though it's actually stored randomly. Why should you care? Real files are stored in pieces scattered around the drive wherever there is space for them. The more free space there is, the quicker the operating system can find a place to store a new piece. That means, if you delete the junk you no longer need (and free up more space) the system actually runs quicker. It helps create space you might need, and allows the operating system to store files for you faster. But there's a second effect. As you delete old files or change them, the pieces get more and more scattered. It takes the 'robot' longer and longer to fetch or display the 'cards' in order. Existing files are fetched and put together 'on the fly' (say, when you request a graphical page or a list of names). But, it takes longer to put together the web page when there are more scattered pieces. So, the other aspect of managing disk space is to keep the pieces of the files more or less in order. A utility that does that is called a 'de-fragger' or de-fragmentation program. You can request that a system administrator run it, or if you have the authority, you can run it yourself. That keeps the 'cards' in order and allows for quicker access to them. So, managing disk space involves chiefly three things: (1) keeping enough space to store what you need to store, and also (2) keeping enough free space to make new file storage quick and (3) making old file retrieval fast by keeping things orderly. When only a few files are involved the benefit isn't worth the effort. But as the number and size of the files grow, to thousands of files or several gigabytes of data, the effect becomes more noticeable. Keeping things organized then makes a significant difference in performance. Much of this can be automated using utilities. Some will delete files in a certain folder older than a certain date. A de-fragger can be set to run automatically during times of light usage, or quietly in the background at all times. Discuss the options with your system administrator and help him or her do the job better by keeping your house in order. You'll benefit by having a better performing web site.

Look Before You Leap

2008-09-09T23:41:00.000-07:00

Companies that offer Internet-connected servers that provide space and bandwidth for a domain, for one or more web sites, are called Web Hosts. Large companies have private networks that allow them to host domains on their own equipment and IP address range. But for the majority of those who want an Internet presence, a 'rented' web host is a necessity. There are a wide variety of hosting plans available. Some are free, others charge up to a $100 or more per month. Some provide nothing but a tiny amount of disk space and minimal network bandwidth. The web site owner is on his or her own for any thing else. Others offer a range of services, including server and email administration, backups, web site design assistance, troubleshooting and many others. In the world of web hosting, you may often find yourself sharing a server with anywhere from one to a thousand or more other web sites. That allows the web hosting company to keep equipment and staff expenses lower. Many web sites are simple and low-volume enough that the arrangement works fine. When you or one or more of the others grow, it may be helpful to consider a dedicated server. A dedicated server, as the name suggests, hosts only your domain. You can put one web site on it, or as many as you wish. You control the access. You may also, as an option, take over much of the server administration yourself. That may save you money on support costs, but cost you considerable time. If you don't have the expertise, you can end up costing yourself much more than you save. In order to carry out those administrative functions yourself, even if you hire help, it's desirable to have some technical knowledge under your belt. Some of that knowledge will be useful, even for day-to-day tasks apart from dealing with emergencies. FTP, email administration, backup methods and other technical areas are among the more common areas you'll need to be at least somewhat familiar with. When your web site grows to a certain size and level of complexity, you'll begin to find it worthwhile to look at implementing a database. But that brings with it a still higher level of ability, both technical and logistical or creative. Implementing a database can be relatively simple. Designing one that provides what you want, with decent performance and maintenance that doesn't become a nightmare, will take some careful thought. Not everyone has the temperament for that type of work, especially those who prefer graphical design, content creation or development, and the many other web site tasks that are part of every implementation. There are other, more low level administrative matters. Managing disk space, maintaining domain names, dealing with registration and changes, and a number of other 'utilitarian' tasks are also not everyone's cup of tea. Some understanding of how DNS works, as well as the design of the Internet itself, are helpful. That provides a good context for understanding the role of some of those tasks. When you begin to seek out a web host to implement a web site, consider all these factors and look in the mirror. What kind of web hosting you should pursue is determined by a combination of who you are and what's being offered. Look before you leap.

Is a Dedicated Server Worth What You Pay?

2008-09-09T23:39:00.000-07:00

In reviewing web hosting plans, many web site owners are faced at some point with the decision of whether or not to pay for a dedicated server. A dedicated server is one which holds your site(s) exclusively. It's not shared with other sites. You then have the option to put one site or many on that piece of hardware. But the decision is never easy. There are multiple considerations to take into account, far beyond just the higher dollar outlay that inevitably accompanies a dedicated server option. Performance is (or should be) a prime consideration for the majority of site owners. Studies show that when a page doesn't load within about 10 seconds or less, almost everyone will give up and go elsewhere. The delay may be caused at any of a hundred different points in the chain between the server and the user. But often, it's the server itself. In any case, it's important to eliminate the server as a possible bottleneck, since it's one of the few points over which the site owner can exercise some control. That need for control extends further than just performance, however. Other aspects of the user experience can benefit or suffer from server behavior. Security is a prime example. With the continuing prevalence of spam and viruses, a server can easily get infected. Having only your site(s) on a single server makes that issue much easier to deal with. With fewer sites on a server, there is less likelihood of getting infected in the first place. Also, since you will place a higher value on security than many others, it's easier to keep a dedicated server clean and your site well protected. You can use best practices in security to fortify your site. Having other sites on the server that you don't control raises the odds that your efforts are for nothing. One way your efforts can get watered down is through IP address sharing. Less sophisticated hosting services will often assign a single IP address to a single server and multipe sites. That means your site is sharing the same IP address with other domains. That leaves you vulnerable in several ways. Virus or spam attacks may target a particular IP address. If you have the same one as another site, one that is more likely to attract hostile intentions, you suffer for and with someone else. In other cases an IP address range is assigned to the server, with each site receiving its own address from within that range. Though better than the one IP:server scenario, this still presents a vulnerability. Many attacks try a range of IP addresses, not just a single one. But even legitimate sources can give you trouble when you share an IP address or a range. If another site engages in behavior that gets it banned, you can suffer the same fate if they ban the address or range. If the miscreant that shares your server/IP address or range is himself a spammer for example, and gets blacklisted, you can inadvertently be banned along with him. Using a dedicated server can overcome that problem. There's a certain comfort level in knowing what is installed on the server you use, and knowing that you alone put it there. But a dedicated server option may require increased administration on your part. If you're not prepared to deal with that, you may have to pay still more to have your dedicated server managed by someone else. All these factors have to be weighed carefully when considering a dedicated server plan.

How To Select A Web Host

2008-09-09T23:38:00.001-07:00

As with many purchases, our first impulse when selecting a web hosting company is to go with the cheapest. Hey, they're all alike, why pay more? Au contraire. There are a number of objective criteria that separates one web hosting company from another and money is only one of them. And not the most important one. Selecting a company based on price alone is equivalent to selecting an auto mechanic on price alone. Sure, he may maintain or fix your car cheaper. But will the car spend all the time in the shop and none on the road? The first consideration is 'horsepower'. Do they have the capacity to carry your load and deliver decent performance? Most hosting companies will advertise that they have huge bandwidth and hundreds of servers. They're usually telling the truth. But there's a difference between existing capacity and usable capacity. If they also have thousands of sites with millions of visitors per day the available or free capacity will be much lower. A big pickup truck may be able to tow 5,000 lbs. But not if it's already carrying 4,999. Be sure to ask about available capacity, and have the prospective company back it up with reliable numbers. If you can't interpret the information they provide, find someone to help you do so. Next, and a very close second, is reliability. A lot of power is worthless if it's cut often. Outages are a normal part of business. Even Google and Microsoft go down from time to time. The difference is, it happens rarely and they have failover plans. That means, if their site/system does go down it's either up again in a flash, or you never see the outage because a backup system kicks in automatically and seamlessly. Be sure to grill the company closely about their up time. They'll often tout 99.6%, or some such figure. But, like the on-time figures of the airlines, those numbers can be shaded by adjusting the definition of 'up time'. What matters to you is whether your visitors will be able to reach your site at any time of the day or night they might want to. Find out what systems, both technical and human, they have in place to deal with failures of all sorts. Servers can go down, networks can fail, hard disks can become defective and lose data even when the other components continue to work fine. The result is YOUR site is unavailable, which is all that matters to you. The web hosting company should be able to deal with all of that and have you up again very quickly. Last, but not least, is security. With the continuing prevalence of viruses and spam, you need to know that the web hosting company you select has an array of methods for dealing with them. That means a good technical plan and staff who are knowledgeable in dealing with those issues. The old saying: 'an ounce of prevention is worth a pound of cure' is more true here than anywhere else. All these issues are central to finding a web hosting company that can deliver the services you need. After those criteria are satisfied by a number of candidates, then you can start narrowing them down by price.

FTP and Other File Transfer Tools

2008-09-09T23:36:00.000-07:00

Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.

Free vs Paid Web Hosting Options

2008-09-09T23:35:00.000-07:00

Everyone likes to get something for free. But as the existence of spam shows, free isn't always good. Sometimes, it's downright harmful. Deciding whether it's worth the cost to pay for hosting involves a number of complex considerations. Hosting companies that offer free services obviously can't stay in business from the money they make from you, since there isn't any. So why do they offer free hosting and how do they make money? Why should you care, so long as you get yours? Because, in reality, there's a price of some kind for everything, even something that's free. Free hosting may come from a company doing a promotion to attract business. They expect to demonstrate their value, then charge an existing customer base fees to make up for what they lost by the (short term) offer. It's in essence a form of advertising. But free hosting is offered by lots of companies that are not dedicated to managing servers for websites. Google, Yahoo and thousands of others provide a modest amount of disk space and a domain name on a server for free. Users are free to do anything they like with it, though if the load becomes excessive you can be shut down. That introduces one of the more obvious drawbacks to free hosting: resource limitations. Typically free hosting offers a relatively small amount of space. That's often enough to host a few dozen pages. But an active site can quickly run out of room. A more serious limitation is load. Free hosting often places strict limitations on the allowed amount of bandwidth consumed. If you become a well-visited site, when users start banging away on the server, you can be asked to leave or simply be blocked for the rest of the month. Or, you may be permitted a certain quantity of total bandwidth use per month. Once it's reached, no one else can reach your site until the beginning of a new month. At the same time, you will certainly be sharing equipment with thousands of other sites. Their load can affect your performance, prompting you to move. Migrating an established site brings with it a number of thorny issues that might be better avoided in the first place. Free hosting has another potential downside: lack of support. When you pay for hosting you typically get, at least in theory, a certain level of support. Backups in case of disaster recovery from a hack or server failure, assistance in analyzing connection problems... the variety is endless. With free hosting you usually get none of that. A company or site that offers free hosting will usually recover a disk or server that fails completely and you'll be back up when they do. But if only selected portions of the drive fail, or you lose a few files through a virus attack or accidental deletion, you have to rely on backups to recover. A free service will usually come with no such option. That may not be a problem if you have a small site. You can make copies of everything at another location and simply recover the site yourself - if you have the discipline to keep it current and the skills to make and restore the copy. Free hosting will typically come with a few email addresses, intended to be used for administration and other tasks. But if your needs grow beyond that, you'll need to seek another option. The email service also comes with minimal oversight. The server may be protected against spam attacks and provide virus scanning. But few free services will provide even minimal help with any issues that arise. But the most serious limitation may have nothing to do with any technical issues. Free hosting services often require that your site's pages carry some form of advertising that pays the host, not you. That may be fine for you, or it may not. Individual circumstances vary. On the other hand, if you're just starting out, a free hosting option can be a great way to learn needed skills and a few of the potential pitfalls. You can set up a site, learn how to maintain and improve it, and not care too much if it gets hacked. Freely hosted sites can be a great platform for learning the ropes. Free services don't usually offer any of the features that an active, commercial site will need sooner or later. So if you plan to grow, it may be reasonable to get the free service for a while, knowing you'll have to migrate when you become popular. But in the long run, you get what you pay for and you may need to pay for what you want.

Email Issues

2008-09-09T23:34:00.002-07:00

When you build a web site, you often provide a means for users to communicate with you. One of the most common 'add-ons' to a web site is the addition of some kind of email access. Email is used to sign users up for newsletters, provide communication for administrative issues and a hundred other uses. But, as everyone sadly knows, email problems can occur. Virus infection is among the most common, though the situation is actually better today than in the past. Huge efforts, and some progress, has been made over the past 10 years to reduce the number and severity of virus attacks. Hackers haven't surrendered, far from it. But they're on the defensive like never before. Many of those viruses were (and are) spread through email, usually in the form of email attachments. That's the source of the now-common advice never to open an attachment from someone you don't know. Professionals will often extend that advice to suggest you never open an attachment that's unexpected, even if it's from someone you know. Well-meaning, but computer-challenged friends often accidentally forward virus infected emails. Spam has taken over the top spot for email annoyances. It's estimated by various different professional sources that 92-97% of all email sent today is spam. While the definition varies, spam is generally regarded as any unwanted commercial email sent by someone whom the recipient doesn't know or have a business relationship with. Spam clutters email inboxes, requires people to sift through to find valid messages, and often contains offensive messages in some form. But, it's a fact of life and isn't going away anytime soon. Even though laws are in place, thousands of spammers continue to risk fines or jail for the chance of making money from that small percentage who will open the unwanted email. Other forms of email problems are even more severe for many web site owners. When the mechanisms fail that they rely on to send and receive messages to and from their users, that's a problem. Dealing with those problems can range from sending an email or instant message to an administrator, to tracking down the right person to get your site removed from a blacklist. Email is the communications vehicle of choice for millions everyday. When the system burps, someone has to take time to do something about it. Often, that means relying on a person who is already overburdened with too many issues to resolve. So, besides pointing out some sad facts or complaining, what's the point? All of the above shows just one more area you should look at when selecting a web host or deciding whether to move to another. Just as with server or network administration, companies vary in their ability to deal with email-related issues. Some are responsive and super-competent. Others, are simply indifferent or worse. And many are in between. Email administration, like server maintenance or network management, is a professional specialty. Skill in one does not necessarily mean quality work in another. Finding a web hosting company and/or system that has few email problems, and solves them quickly when they occur, is an important task. Spend some time researching who provides superior support in email. You'll be happy you did.

Domain Name Changes and How They Affect You

2008-09-09T23:34:00.001-07:00

New domain names are registered all the time, and ones previously registered expired. Sometimes that's the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else o use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to ust let it go or sell it. When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties. One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. P addresses are what are actually used 'under the covers' when one computer communicates with another. Note that there isn't always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we'll stick to the common case here. DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request o be forwarded when the particular DNS server doesn't have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low. n the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was. A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed. The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world. Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching. In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don't move your address or change your name every minute. Since that's true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn't have to be communicated with every request for a web page or data. A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that's your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed. Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random. But DNS servers don't do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies. That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the 'official' range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that's an average. The actual time in any given case can (and does) vary widely. In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can't be resolved properly, you don't reach the server you want. Your browser points to the old one (in the rare case it's still accessible by that name and address), or it simply reports there's no such name at that address. So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being 'not at home' when they call.

Changing Web Hosts, Pitfalls and Planning

2008-09-09T23:31:00.000-07:00

At some point, nearly everyone finds it necessary to change web hosts. It may be just a migration to another server, or it may be changing web hosting companies entirely. Either way, the process is fraught with potential dangers. But there are ways to minimize the odds of problems and maximize your changes of a smooth migration. Plan, plan, plan. Make a very detailed list of everything that is on your current system. Review what is static and what changes frequently. Note any tailoring done to software and files. Be prepared to remake them if the systems aren't transferred properly or can't be restored. Keep careful track of all old and new names, IP addresses and other information needed to make the migration. Backup and Test Backup everything on your system yourself, whenever possible. Web hosting companies typically offer that as a service, but the staff and/or software are often less than par. Often backups appear to go well, but they're rarely tested by restoring to a spare server. When the time comes that they're needed, they sometimes don't work. Do a dry run, if you can. Restore the system to its new location and make any needed changes. If you have the host name and or IP address buried in files, make sure it gets changed. This is often true of databases. SQL Server on Windows, for example, picks up the host name during installation. Moving a single database, or even multiple ones, to a new server is straightforward using in-built utilities or commercial backup/restore software. But moving certain system-related information may require changing the host name stored inside the master database. Similar considerations apply to web servers and other components. Accept Some Downtime Be prepared for some downtime. Very few systems can be picked up, moved to another place, then brought online with zero downtime. Doing so is possible, in fact it's common. But in such scenarios high-powered professionals use state-of-the-art tools to make the transition seamless. Most staff at web hosting companies don't have the skills or the resources to pull it off. Prepare for Name Changes One aspect of moving to a new host can bedevil the most skilled professionals: changing domain names and or domain name/IP address combinations. When you type a URL into your browser, or click on one, that name is used because it's easier for people to remember. www.yahoo.com is a lot easier to remember than 209.131.36.158. Yet the name and or name/IP address combination can (and does) change. Still, specialized servers called DNS (Domain Name System) servers have to keep track of them. And there are a lot of them. There may be only two (rarely) or there may be a dozen or more DNS servers between your visitors' browsers/computers and your web host. Every system along the chain has to keep track of who is who. When a name/IP address changes, that pair has to be communicated to everyone along the chain, and that takes time. In the meantime, it's possible for one visitor to find you at the new place, while another will be pointing to the old one. Some amount of downtime will usually occur while everything gets back in sync. The Little Gotchas But even apart from name and IP address changes, there are a hundred little things that can, and often do, go wrong. That's not a disaster. It's just the normal hurdles that arise when changing something as complicated as a web site and the associated systems that underlie it. Gather Tools and Support Having an FTP program that you're familiar with will help facilitate the change. That will allow you to quickly move files from one place to the next to do your part to get the system ready to go or make repairs. Making the effort to get to know, and become friendly with, support staff at the new site can be a huge benefit. They may be more willing to address your problem before the dozen others they have to deal with at any given moment. Ok. On your mark. Get ready. Go.

Do It Yourself Administration, Things to Consider

2008-09-09T22:41:00.000-07:00

The choice of whether or not to try to administer your own web site brings with it a host, pun intended, of issues. For most web site owners, the primary focus is naturally on creating, maintaining and enhancing the site. That often is just part of managing an entire business, for which the web site is just the means to an end. That implies there will be little interest in or time left over for technical administration like database maintenance (tuning, space management, security, bug fixes), establishing and maintaining backups to ensure they're successful and usable, email administration, disk space management, applying operating system fixes for bugs and security, and other tasks. But cost is always a factor in any business. Paying for technical help can burden the budget of a new and struggling business. Consulting fees can range from a few dollars an hour to over $100. On the lower end, the poor skill level and quality of work will make it not worth even that small amount. On the higher end, you can quickly rack up expenses that will bust your business. Permanent employees are usually somewhere in the middle of that range when you add up salary, employment taxes and more. Often, server and/or web site administration can be paid for as part of the web hosting package. That cost is usually lower than independent contracting help, but those staff are usually tasked with maintaining dozens if not hundreds of servers and sites. They can, therefore, give very little individual attention to yours. Often, novice web site owners are intimidated by some of the technical requirements for server or site administration. But, as with anything, a little familiarity can show that the knowledge required is more modest than one might expect. Administration in many cases involves fairly elementary, and frequently repetitive, tasks. These can be learned easily. Using a test site or a free hosting service is a good way to practice and learn without risk or cost, other than time invested. Once that initial hurdle is jumped over, administration can be done quickly and some even find it interesting. It allows the site owner to exercise additional control over the total product, and there's satisfaction in being able to say 'I did that' even if you prefer not to do it forever. That real-life learning experience also allows the site owner to better judge any consultants or staff that are hired. It's much easier to judge if someone is providing you with an accurate assessment of a problem if you've solved it yourself. Any time-estimate they provide to fix it can also be better calculated if you've had to do it yourself. Every web site relies on a variety of factors, usually unseen, in order to continue to function properly. But the fact is that they misbehave from time to time. Deciding whether to tackle those problems yourself depends on your available time and skill set, and what it will require to get things back on track. In other words, it's a standard cost-benefit analysis that everyone has to undertake every day in life.

DNS, How The Internet Keeps Track of Names

2008-09-09T22:40:00.000-07:00

The way computers communicate is, in a way, very similar to something very familiar: the postal system that delivers letters and packages. Here's how... The Internet is just what the name suggests, a large inter-connected set of networks. But those networks are pointless without the one part that forms what is called their 'end-nodes', otherwise known as computers. Those computers often need to share information because the people who use them want to share information. But, in a system where there are millions of separate computers, how can you enable them all to communicate? One very important feature of that solution is performed by something called DNS, the Domain Name System. Every part of a network that is going to send or receive information is assigned an IP address. That's a numeric identifier that uniquely specifies a particular 'node', such as a computer, a router that directs traffic or other component. They look like this: 209.131.36.158 But those numbers are more difficult for people to remember and work with. They also aren't very attractive from a marketing perspective. So, a naming system was layered on top of some of them, mostly the computers involved, though routers have names, too. But once you have a system that associates a unique IP address to a given name, you need some way of keeping track of all of them. That's carried out by several different pieces of the system: Name Registrars, DNS Servers and other components. The Name Registrars, overseen by IANA (Internet Assigned Numbers Authority) and other international bodies, provide and keep track of domain names. When you register with GoDaddy or any of a hundred other intermediate companies, ultimately that information makes its way into a number of specialized databases stored inside DNS Servers. A DNS Server is the hardware and/or software that tracks and forwards the IP Address/Domain Name pair from one place to the next. In many cases, there are a number of them between your browser and the remote computer you want to share information with. Suppose you request information from, say, Yahoo's site by clicking on a link on their site. DNS resolves (translates) the name of WHO IS making the request and OF WHOM, to addresses, then passes the request through the network to the requested IP address. The requested data is then passed back through the mesh of network components to your computer and displayed in your browser. Whether the communication is between a desktop computer and a server somewhere, or between one server and another, the process is essentially the same. DNS servers translate names into IP addresses and the requests for data are forwarded on. In some cases those DNS servers are part of a specialized network computer whose sole job is to do the translation and forwarding. In other cases the DNS software may reside on a server that also houses a database of general data, or stores email, or performs other functions. But however complicated the chain or the parts, the basic process is simple. Translate the name to an address, just as the postal system does. Whether international or local, your name is associated with an address, and the deliveries are made to the address, then forwarded to a particular name.

Databases, What Are They and do you need one?

2008-09-09T22:36:00.000-07:00

'Database' is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they're essential is often not clear to novices. A database is a collection of organized data, stored in files that have a specific structure. It's that organization and structure that allows for easy and rapid storage and retrieval. The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it's worth. Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept 'tuned' for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures. With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime. Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn't even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play. Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called 'tables'). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, ...) in another? Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new. Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider. It's true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them.

When Changing Web Hosts

2008-09-09T22:35:00.000-07:00

Nearly everyone will want to change to a new web host at some point. It may involve just changing out old hardware for new. It usually means finding an entirely new web hosting company. When faced with that decision there are a number of issues to be considered. Swapping hardware and/or software is a fairly straightforward decision. There are two possible scenarios. Either you maintain your own hardware and software at a facility managed by others, or you are considering upgrading to newer (usually more expensive) systems maintained by others. In either case, it's simply a matter of estimating the cost and the short-term impact versus the long-term benefits. If the system(s) you currently use are short on capacity, sooner or later you'll be sufficiently motivated to make the change. Either the hardware will become unreliable or loaded to the point you'll be forced to migrate, or your needs will expand enough to justify the effort and expense of moving. Similar considerations apply to the scenario in which you rely on the web hosting company for everything, and want to find someone else to rely on. Regrettably, that's a very common situation. Many web hosting companies provide systems and staff that sooner or later fall below an acceptable level. Most people make the decision to change based on emotion. That's not entirely bad. Emotions incent you to take action. But you need to keep a cool head, too, in order to calculate your long-range self-interest. Bearing some minor inconveniences from time to time is usually worth the trade off. When it begins to affect your site to the point you're losing visitors, it's time to make a change. To get a more objective handle on when that point is reached, reach for some numbers. Maintain, or get from the hosting company, a factual report about availability and current usage. If the server is down so much, or so heavily loaded, that it drives your visitors away, it's time to take action. There are other less easily quantifiable but equally important factors, as well. You will at some point need to communicate with one or more persons who help maintain your site. Even if you do all your own server, database and web site maintenance, someone behind the scenes is helping to keep things running smoothly. That's called 'infrastructure'. If the road you drive on has potholes, it's not enough that you can fix your own car. In terms of network bandwidth and availability, server capacity, disk space, security and a whole array of other aspects, the web hosting company has to have competent people who care (and are allowed) to do the job well. When the company's people fall down - because of incompetence, lack of resources or absence of a culture of excellence - or for any other reason - your web site suffers. This issue more than any other is what drives people to seek another web hosting company. Even if you choose well at the outset, things can change. Management changes, staff changes and companies are taken over by other companies. Sometimes, it isn't simply a matter of swapping out an unreliable piece of hardware or software. When it's time to swap out people, you look for the same aspect: doing the job required.

Bandwith and Server loads, whats that?

2008-09-09T22:31:00.000-07:00

Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes.
So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.

Web Hosting - Why Backups Are Essential

2008-09-09T22:26:00.000-07:00

One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort.

Web Hosting - All About Domain Names

2008-09-09T22:15:00.000-07:00

"What's in a name?" Shakespeare asks in Romeo and Juliet. In the case of your web site the answer is: quite a lot. A domain name is the English (or other) language designator for your site. Because of the way the Internet functions, that name is associated with an IP address, a numeric identifier that computers and network components use to connect a browser to a web site. It's not mandatory that a site has a name. But directing visitors by IP address can quickly generate difficulties. Having an IP address IS mandatory, since it's ultimately the way a web site is located by other computers and network software. In the early days of the Internet the name was chosen carefully in order to help a person remember the URL. That made it easier to type, too. With hotspots on a page, great search engines, social networking and other contemporary tools, that's not as important now. But from a marketing perspective, it still helps to have a good name. It's still beneficial to have a site called 'CheapTVs.com' if what you sell are inexpensive TV sets. Calling your site, 'InexpensiveElectronicVisualDisplayDevices.com' may describe your business in some way, but it's a little harder to refer a new person to your site. Which name you choose can, therefore, affect how much traffic your site gets, how soon. Sooner or later, if you have information and/or products/services that people want, word will get around. But having a good name can certainly help. Love them or hate them, the Google company chose well. Of course, the fact is that there are millions of web sites around the world. That means, you don't necessarily get the name of your first choice. ICANN (Internet Corporation for Assigned Names and Numbers) is the internationally recognized authority for managing IP addresses across the worldwide Internet, along with the top-level domain name-parts (.com, .net, .org, .edu, and so forth). But registering a name is done by simply contacting any of a hundred organizations that work as intermediaries to establish and track the names. GoDaddy, Register.com, Network Solutions and a great many others provide the service for anywhere from free to a few dollars per month or year. You contact them by navigating to their web site. Then, using a feature they all provide, you can select a possible name. They use something called whois and other software to determine if the name is already claimed. Or, you can check yourself at http://www.whois.com/. Registration is for a limited time, but typically renewable in perpetuity provided you pay the (usually annual) fee. You may have to go through several choices to find a domain name that isn't already in use. With so many millions of sites, the odds of you getting your first choice is slim, unless you have a highly unusual imagination. But, it's also true that domains tend to die or expire. As they do, the name becomes available for use by someone new. A method for getting on a 'waiting list' is available. You register the name you want and if and when the name becomes available, you are offered the chance to claim it. Naturally, there's competition even on the waiting list for 'good' names. There are many different ways of establishing priority that vary by company. At any given time there are thousands of so-called auctions going on to bid on names. Give some thought to your new domain name and research its availability, but don't stress over it. The name isn't everything. After all, if Google had built a search engine that delivered usable results only 10% of the time, their name would be mud.