Welcome to www.unileaks.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.
Web Hosting - Bandwidth and Server Load, What's That? 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.
Judging by Appearance ? It Happens in the Workplace This is one of the old sayings that really does come true, the clothes do make a person. What does it mean? For many people, it means that people judge by the clothes you wear. This is especially true in the workplace, but also for everyday life. Many companies nowadays have a dress policy in place to keep the appearances at work up. Reasons why companies have dress policies are of a great variety. Here is a review. One of the biggest reasons for companies to require nice appropriate clothing at least in their office area is visiting customers. If your employees need to be in contact with customers on daily or weekly bases or if customers do visit your offices in general, it is important that your employees make a good first impression. First impressions are very much guided by what you are wearing, your facial impressions and body posture. Therefore, if your customer see your employees working on their desks, it is important that the employees are dressed appropriately. For most workplaces this means a button down or polo shirt, dress pants or casual dress pants. In some instances, it is important for the employees to wear a tie and suit. For women, the codes are equivalent what the style of the clothing is referring to. Imagine what would happen if a customer comes into a company and the employee receiving the customer wears dirty, spotty, old and ripped clothes. In society that does not make a good impression, then the customer will most likely not want to do business with you. Another reason of why companies and employers would judge by your appearance is called professionalism. In the picture of professionalism at the workplace includes good appropriate clothing. It belongs to being a good employee as much as doing your job right and being polite and respectful to your boss and colleagues at your workplace. In society much is judged by the way you dress. If you have ever walked into one of the better department stores with a set of old, worn clothes, what kind of response do you get from the sales person? Often times they think you do not have enough money to buy here anyways and that is the way they treat you. They may not even give you the time of day, even if you have a lot of money. They judge you by what you have on and this is certainly the case in the workplace as well. If you want to project a good image, then take a good look at what you wear before you step out of your door in the morning. There are many places where a dress code is required or expected, such as the church, the opera, the theater, better restaurants and many other places. The workplace is just one of many and whether you like it or not, appropriate clothing is what can make or keep you get the job. Many Internet sites, books and people that offer advice on interviews and getting that job, will emphasize the importance of nice appropriate clothing and the impact it can have when you wear something that stands out from the crowd. Most people have been raised to think that proper dress attire is what you should wear at work, but for some it still is more a mystery to them than anything else.
Web Hosting - Why Backups Are Essential 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.