Welcome to taxkingsandqueens.com
|
Web Hosting - When Changing Web Hosts
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.
Web Hosting - Sharing A Server – Things To Think About 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. Software company patent A Software Company Patent is the Door to a World of Confusion There is no universal understanding of exactly what a software company patent is. In general, owning a patent allows a company certain rights (or exclusivity) for a prescribed amount of time. Individuals or corporations seeking a patent must apply for a patent in each and every country in which they wish to have one. Unlike copyrights, patents are not automatically granted to applicants and can take quite a while in order to be approved. Another thing to remember, particularly with a software company patent, is that a patent may issue in one or more of the countries in which you've applied but not all of them. The real problem lies in the fact that there really is no central agreement about what a software company patent actually grants among any of the nations so those who are awarded patents may not be getting exactly what they think they are getting in the process. With no universal agreement there really can't be universal enforcement about the laws and the rights surrounding a software company patent. The growth of Internet business and e-commerce in general has led to many patent applications for software, particularly software that was designed for specific business applications. The problem is that while the cases are granted and successfully tried and defended in some countries, other countries offer no enforcement or legal recourse for those who do not honor the software company patent even if the patents were granted in those countries. The fine line between nations about what is and isn't patentable is another challenge when it comes to establishing and honoring patents. In other words, the issue of a software company patent is a rather confusing process at best. Patents differ greatly from copyrights, which are issued automatically and recognized and enforced internationally. Copyrights protect the source code of software from being copied and registration is generally not required in order for your work to be protected. Lately there is a new term, copyleft, which is an obvious play on words and represents the rights to not only redistribute the works that are covered by this but also to modify and freely distribute those modifications. This term is very much in the spirit of many open source types of software and music. The catch for copyleft protection is that the newly created work be distributed in the same manner and spirit in which it was received. In other words if you were freely given the software, then you must freely provide the improvements and modifications you made to that software. Of course this is a long way from the idea of a software company patent. It is also important that you are sure you understand exactly what you are applying for as far as your patent goes. Different countries will grant patents for different things and those are closely regulated and carefully regarded when it comes to software-know what you are applying for and understand what you are being granted. A software company patent means different things to different people in different places and it nearly impossible to get other countries to honor a patent that they would not have granted at the same time they shouldn't expect other countries to honor patents based on their decision to do so either. One unfortunate circumstance surrounding patents is that there seems to be an unequal and obvious disparity between the haves and the have not's. Patent enforcement for software, unlike literature and music is largely subjective. In literature and music, it is rather obvious that the copyright has been abused or that the work has been copied, this isn't as simple with software which is one other reason that software company patent is such a hotly debated subject in the software industry. |