Welcome to elreno.org
|
Web Hosting - Is a Dedicated Server Worth What You Pay?
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.
Copyright music expiration For Many Copyright Music Expiration is a Luxury for Worry If you copyright music, expiration isn't something you have to worry about, at least not in your lifetime. The music that you've written is copyrighted the moment you've put it onto paper or recorded it being played. The reason you don't have to worry about expiration is because the music is protected until 70 years after the death of the author. In the case of your music, that author would be you. This rule about copyright music expiration was first put into place so that the families and heirs of an author could still earn royalties even after his or her death. Ultimately this means that if you've taken the steps to copyright your music and have registered the copyright then your music will be protected throughout your lifetime until 70 years after you or the last surviving author (assuming a collaboration) are no longer living. Copyright music expiration is not something you should make a primary concern unless you are having issues of someone respecting and/or honoring your copyright at the moment. You should take comfort in the fact that as long as you are alive you are the only one who can assign your copyright to another person and as long as you haven't given up your ownership of the music it still belongs to you. This is different however if your copyrighted music was work made for hire. If that is the case then you cannot have ownership of the music, as it never legally belonged to you no matter what form it was in when it changed hands. Works made for hire have different copyright music expiration than those that were owned by the creator. With works made for hire, the copyrights are in effect for 95 years from the original publication date or for 120 years from the creation of the work whichever of the two is shorter. For most beginning musician’s copyright music expiration date isn't as important as getting that first gig or earning that first dollar as a result of the music he or she writes and/or plays. It's about art for many and about survival for others. The latter are quite often the ones that are taken advantage of. These are the authors who don't protect themselves as they should and end up failing to register their music because the idea of buying food seemed more pertinent to survival at the moment. This is often the case, particularly among street musicians and it's something that was becoming a growing problem immediately after hurricane Katrina devastated New Orleans taking with it many of the homes of starving musicians along with many pieces of music that will never become copyright music, expiration or not, those works are gone forever except in the mind of their creators. who could barely scrape together the money to pay $100 a month for a hovel they shared with 6 or 7 other people in order to keep expenses down and avoid living on the streets. The building not only of homes for those musicians displaced as a result of Katrina's devastation is wonderful but even more than that is the fact that there are organizations that are dedicated to creating a community for these musicians so that maybe many of the struggling artists won't be taken advantage of or have to face the decision to register their music in order to protect and copyright music expiration for their future heirs or to risk loosing their claim over the music they wrote in order to eat or pay the rent or buy groceries. 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. |