DedicatedHosting.com - We're Totally Dedicated to Hosting

This article discusses the pros and cons of self hosting and comparing that to dedicated hosting. While self hosting has some advantages, it is best to leave mission-critical applications on a dedicated hosting environment.

What is Hosting?

Let’s define hosting as running a server that is, or can be, connected to the world wide Web, and further define a server as a computer that can receive requests for data from external sources (‘clients’), process the requests and return (’serve’) the requested data in the appropriate format and communication protocol. Client devices can be desktop computers as well as smart phones and other digital devices.

There are many types of servers, which vary in the data and function they preform, some of which are:

• Web servers – used to transfer the content of Web pages in a protocol known as http (hypertext transfer protocol) for display by browsers. The Web pages can be static text files, or dynamic pages created or modified on the fly on the server, using a scripting language.
  
• File servers – often used in offices to serve data from a central repository to users’ desktops, but with the rise in telecommuting and cloud storage, are increasingly used through the Web.
  
• FTP servers – used for serving (large) files using the file transfer protocol (ftp).
  
• Mail servers – used to send and receive electronic mail.
  
• DNS servers – translate Web domain names into the numerical addresses used by computers.
  
• Database servers – contain data and processing software (database management system) which receive requests written in a Structured Query Language (SQL) and respond by sending the requested data.
  
• And the list goes on.

Servers can be shared by many users (a shared server), or a single user (a dedicated server). Each user in a shared server gets a portion of the server’s storage space and processing power. The degree of isolation between individual users on the machine can vary depending on the hardware and software used. ‘Virtual private servers’ (also known as ‘virtual dedicated servers’ and other names) and ‘cloud servers’ use virtualization software to isolate users and provide service level guarantees beyond those of shared servers.

Why Host at Home?

Hosting at home can be tempting to the technically savvy, do-it-yourselfer. It has the same appeal as growing a garden, cooking from scratch, renovating a home, or rebuilding a car engine. It can put to use an old or unused computer, without the expense and hassle of using a professional ISP. It is a way to dip a toe into hosting, without the cost and commitment of leasing a server.

From the perspective of someone running or working in a business, there are a number of other use cases where home hosting can make sense, especially for the person that spends much time on the road, or works outside the office. For example:

• An ftp server, for keeping and serving documents and other files.
  
• A Web server, for hosting a blog, wiki, or html Web pages.
  
• A development server, for developing, maintaining or documenting software.
  
• A testing server, for checking the latest patches or software updates.
  
• A production server, to customize software for demonstrations or client projects.
  
• A backup server, in case the office network is inaccessible, outside office hours or due to service disruptions.
  
• A streaming server, for streaming or downloading personal audio and video files, for examples a server used to record TV shows and radio programs for watching on the road.

The Advantages of Self Hosting

Self hosting has a number of things going for it, which may be grouped under control, convenience and flexibility, and cost savings.

Control:

Direct physical access to a server gives the highest level of control, which has a number of benefits:

• A self host can do things that no ‘normal’ data center would ever allow (except ‘bulletproof hosting’ providers, popular among criminal groups, spammers and file-sharing services, that make a virtue of being impervious to legal threats and blocks). One can host IRC (chat) channels, give users shell or even root access, deploy outdated or insecure software, allow or send spam, violate copyright and decency laws, etc. While these practices, in general, are ill advised and are likely to end in grief or prosecution, the host has the last word.
  
• Self hosts can do things a data center is not equipped to do, such as connecting to phones, cable and satellites, recording and streaming audio and video, providing access to music, video collection, etc.
  
• Data centers subscribe to the ‘good, better, best’ philosophy, tying together processor speed, memory, storage and bandwidth, and coupling higher prices to higher specs. With self hosting, one can configure the server in a way that matches specific needs, even if the system is unorthodox. For example, a server that stores a video and audio collection for occasional access needs lots of storage, but little CPU or RAM. In contrast, a server used to dynamically customize a small amount of static content for lots of connections may need a very fast processor and loads of CPU, but a very small drive. The home host may build servers with such hardware specifications. Finding a data center offering such servers is tough.
  
• With self hosting, one can take the server down any time, for any duration, and at any frequency. In a data center a downed server would trigger alarm bells from the monitoring software, and lead to calls from technician or even an automatic restart, unless coordinated and scheduled in advance.

Convenience and Flexibility:

Self hosting can sometimes be more convenient and flexible than hosting at a data center:

• Hardware modifications do not require coordination with data center staff. Work can be done at any hour of the day and night, and can be repeated as frequently as desired.
  
• Changes made to the server can be instantly viewed and verified. No more delegation, communication or waiting for third parties to confirm the server is ready.
  
• Software changes and upgrades are a breeze with physical access. Using a CD/DVD is still the quickest and easiest way to upgrade or replace software, even more so when the target for replacement is the operating system itself.
  
• Software updates, content modification, and server administration can be done without any need to use ftp and secure login to a remote computer.
  
• For most users, a graphical user interface is easier and more efficient than the command line. Upgrading or managing a server remotely, using or a remote desktop software, can be sluggish and frustrating.
  
• As fast as the server goes up, it can go down. There is no need to explain, no need to negotiate with the hosting provider, no contract to cancel and no worry that the ISP account is closed and billing is settled.

Cost Savings:

Self hosts can deploy cheap dedicated servers, leading to affordable hosting, while running the equivalent of a dedicated hosting solution.

• The use of equipment that already exists at the home (computer, broadband modem/router, real-estate, electric power) means that starting to host is inexpensive. It is also possible, though not recommended, to use an ancient computer for the job, at least for proof of concept.
  
• Operating expenses are low, compared to a data center server lease. A server at home is the equivalent of a dedicate server, but the cost is lower than that of a typical shared server.
  
• Shutting the server down does not have any serious negative financial impact, as opposed to closing an account with a data center.
  
• There is no risk of bandwidth overages, since it is capped by the home service provider, and thus no risk of having to pay expensive bandwidth overage charges. There is also no risk of CPU, memory or storage overages.
  
• The cost is very predictable. There is no chance of bursting charges for CPU, memory or storage usage, unlike pay on demand cloud hosting.
  

The Problems with Self Hosting

Self hosting has quite a few shortcomings, too, from uncertainty of service continuity, through performance and quality of service issues, to what can be described as ‘nuisance’ issues – difficulties caused by hosting at home. The problems mostly stem from the fact that residential properties are not well supported by the Internet service providers, and the services performed by the data center staff have to be done by the host.

Uncertainty of Service Continuity:

• Even under normal conditions, residential connection speed will at times be slower due to congestion at the local or regional level. Regular disruptions occur at times of high usage, such as evening hours and weekends, when home users go on the net, and the server takes longer to deliver. It is impossible to predict in advance how bad the performance degradation would be. That is particularly true of cable Internet, which is shared by all users on the local network.
  
• Residential networks are also subject to sporadic periods of low performance. Unexpected disruptions are due to infrastructure (power, communication) failures and to planned and unplanned maintenance work by the ISP. The utilities treat residential service as a lower priority, and do not guarantee service continuity. The server may be inaccessible for many hours without advanced warning and with no recourse.
  
• ISP policies are subject to change without notice or consultation with subscribers. Ports and services can be blocked or throttled at times of high use or network congestion, and providers have the right slow or stop outgoing net traffic without notice to users. You may find suddenly that the server is not accessible and you would have to scramble to find out why that is, and whether the disruption is temporary or permanent
  
• If you move to a new address or replace your home service provider, your ability to host might be compromised. Similarly, mergers or sale of your ISP, or a switch in the local cable provider, can unexpectedly change your service contracts and what you can do with a home server.
  
• Lack of redundant systems at the home means that service disruptions (for example weather related power outages, cuts in optical cable) can cut your server off.

Performance and Quality of Service:

• The typical DSL connection (at least in the US) is asymmetric, offering an upload rate that is a fraction of the download speed. This may be enough for personal Web pages, but if the hosted site becomes popular, or if there are large files for viewing or download, lags or connection failures (time-outs) are to be expected.
  
• Many providers oversubscribe their network, that is, sell more bandwidth than is actually available from the infrastructure, under the (mostly accurate) assumption that their customers use only a fraction of the promised speed. Customers who come close to full utilization of their bandwidth are often either throttled down, shut down, or bumped to a higher cost service level. A Web host using a residential network should be prepared for such a possibility.
  
• Residential Internet does not come with a service level agreement (SLA). If the connection is down for a day or two, all one can expect to get is sympathy, a possible apology, and maybe a small refund.
  
• There is no easy modification path for servers in a residence. Unlike hosted servers, one can not upgrade or downgrade easily. A faster pipeline (fractional or full T1 connection) costs hundreds of dollars in additional monthly charges, and may take days or weeks for installation and setup. In contrast, with a server at a reputable data center, processing power, storage, memory and bandwidth can be quickly and easily be scaled up (or down). Scaling of cloud servers can be automated and performed on demand.
  
• Homes do not have redundant electric grids, multiple bandwidth providers (carriers). Power and connectivity disruptions can not be mitigated by using an alternate grid, diverting traffic to a server in another location, or using an alternate route to the Web, as a data center can do.
  
• There is no easy way of bursting or adding a server in a residence. Unlike data center hosting, cloud hosting solutions or hybrid hosting solutions, if demand goes up, you can not add bandwidth, add more servers, or increase storage on demand. If the server is swamped, performance will suffer.
  
• Home servers are inadequate for game hosting, as the home infrastructure is insufficient.  Likewise, providing virtual hosting from a home is ill advised.

Nuisance Issues:

• Service provider policies: DSL and cable providers are not always hospitable to Web hosting. Some ISPs block ports needed for hosting (for example, http, ftp, sftp and ssh ports). Others explicitly forbid Web hosting in their contracts, or have contract clauses which allow them to raise prices and penalize customers who run servers. At the least, make sure that your hosting activities are not violating any ISP policies and, whenever possible, use a host that does not block ports and supports Web hosting, before putting the server online.
  
• IP Addresses: Most ISPs provide dynamic IP addresses to home users, so the server’s IP address changes every few hours or days. A fixed IP address, which is better for hosting a server, may be available at a premium. If the ISP does not offer fixed IP addresses, register the site’s domain name with a dynamic DNS host, and install a scripts to update the IP address either whenever the home IP address changes, or at regular intervals.
  
• Managing dynamic IPs: There is a sweet spot for DNS update frequency – do it too infrequently, and your server will have periods when it is unreachable; Do it too frequently, and your dynamic DNS provider will complain and ask you to lower the update rate. It is best to also monitor the server regularly to make sure it is visible at all times – to ask a friend to check it, or use a professional monitoring service, just in case the update script fails. Complicated, but still not an insurmountable hurdle to overcome.
  
• Obtaining redundant connectivity: Using multiple network providers (cable and DSL, or two separate ISPs and phone lines) is a possible way to get connection redundancy at home, as long as the providers do not use the same Internet backbone. This requires configuring the server or router to use two networks simultaneously, or having a system in place to alter the IP address when the backup connection kicks in.
  
• Lack of power redundancy: Installing a UPS is an appropriate solution for short term power-outs, and a generator can keep the server, modem and router running during longer periods of power loss. These add breathing room, but are not a perfect solution for long periods of power loss, and may be impractical in many situations (use of a generator in a condominium or high rise comes to mind). It is also quite possible that the power loss will extend to the local Internet hub, which may not have alternate power source.
  
• Choking personal bandwidth: Bandwidth at home is shared between all connected devices. When the server is busy, everyone else waits for Web pages or audio/video streams to download. So, once a self hosted site gets popular, be prepared for complaints from members of the household. This, by the way, is a two way problem – when a family member or a guest is watching YouTube, downloading a movie or a large file, or using a peer to peer application (bit-torrent, video conferencing, Skype or other Voice over IP system, etc.), the server will be slow. A second phone line, dedicated for hosting, is a possible solution, at a moderate expense.
  
• Noise and heat: Any server, and especially older computer models, inevitably generates noise from the processor and power supply fans, from the hard drives and from other mechanical storage devices. The constant hum, accentuated by the occasional whir and screech, and beeps from the UPS, can get quite annoying after a while, especially if the server is in a common area. The heat generated by the server, which increases with the popularity (and higher load) of the site, may require a fan or air conditioner to make the area habitable. In the summer, especially in hot and humid climates, cooling may be required to keep the server from overheating and possibly even locking up.
  
• Unless one physically splits networks, desktop computers and the server share the same network. While a firewall on the router can block access to the desktops, the server must be open to the internet. Incorrect configuration or bugs in the firewall can expose the internal network to hackers, and put confidential personal information, credit and bank statements and other financial data at risk. Make sure that you prevent access to desktops using software firewalls, and of course secure your server. Whenever practical, a separate networks for the server and the home network is recommended.
  
• When one hosts at home, there is no one else to blame. The responsibility for securing the server, auditing, patching and updating the software, intrusion prevention, backing up and restoring data, diagnosing problems, maintaining hardware and restarting the server when necessary falls on the host. This is a 24 x 7 x 365 job, that is not as much fun as it sounds. And any ‘xplaining to do’ is the host’s to handle – there is no data center to blame…

Alternatives to Self Hosting

The closest analogs to self hosting are (unmanaged) dedicated hosting and colocated server. In either case the server is hosted at a data center. With colocation, the host owns the server, while with dedicated hosting the service provider owns the server and leases it to the host. Prices vary between providers and locations, but expect to find a solution for $75-100/month (plus a small setup fee in some plans). Colocated servers are often limited to 1U rack mounted servers, and larger form factors (like a tower) cost more.

Colocation arrangements usually allow the host or a representative physical access to the server, either during working hours or around the clock. Thus, the level of control on the hardware and software is high, though the ISP usually requires compliance with its acceptable use policies. Alas, colocation facilities are rarely within driving distance. Dedicated servers offer some flexibility in software and operating systems, but choices are more limited than those available to colocated servers.

Data centers are optimized for high availability and service continuity. The infrastructure and the technical support are primed to keep server downtime to a minimum. With both dedicated hosting and colocation, the host benefits from the data center infrastructure – fixed IP addresses, redundant power, redundant connection to the web, quality data networks, server (ping) monitoring, free reboots and occasionally remote reboot capabilities. Additional technical support and server management are available for a fee. Bandwidth is usually burstable, and is soft capped, meaning it is possible to go over the contracted amount for additional charge. Network capacity is hundreds of times higher than a typical residential line.

The negative aspects of unmanaged dedicated hosting and colocation are the possibility of high overage charges if the server is compromised or becomes popular, the hassle of remote server management, and the limited geographic availability of colocation facilities.

Conclusion

Self hosting has both advantages and disadvantages. Its value and appropriateness depends on the situation. Hosting a high performance site, a mission critical site, a site which makes a profit, or a site hosting other users, all of which need availability and reliability, should be done at a professional data center, either on a leased server or through co-location. A high quality data center guarantees redundancy, monitoring, and support around the clock, so the site is always on, always reachable, always earning.

On the other hand, a personal or hobby site, where performance is not as important, and down time is of no great consequence, is well suited for hosting at home. Hosting a personal site at home is a great learning experience, one that makes the practitioner a better system administrator and host.

All things considered, the headaches associated with self hosting may outweigh the benefits. The fun pales in comparison to the noise, heat and stress of recovering from a power cut, failed hardware or a hacker attack. Taking these into consideration, it probably is best to limit hosting at home to ‘proof of concept’ servers, and use a data center for ‘live’ servers, even for personal use sites.