You can definitely use your PC as a server. But you must be aware with certain cons of it.
* Dealing with service providers, part 1: 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. Frustratingly, ISP policies are ofter subject to change without notice or consultation. At the least, home hosts are advised to make sure they are not violating any existing policies and, whenever possible, use a host that does not block ports and supports Web hosting, before putting the server online.
* Dealing with service providers, part 2: Many providers oversubscribe their network, that is, they sell more bandwidth than is actually available in the infrastructure. They do so 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 contingency.
* IP address issues: Most ISPs provide dynamic IP addresses to home users, which means that the server's IP address changes every few days or even every few hours. A fixed IP address is better for hosting a server, and is recommended even if incurs an additional cost from the ISP. If the ISP does not offer fixed IP addresses, it is possible register the site's domain name with a dynamic DNS host, and install a scripts to update the IP address at that DNS host either whenever the home IP address changes, or at regular intervals. There is a sweet spot for the update frequency - do it too infrequently, and your server will have periods when it can not be reached from the outside; Do it too frequently, and you will get a nasty email from your dynamic DNS provider, asking you to lower the update frequency. 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. If it sounds complicated, it's because it is, though it is not an insurmountable hurdle to overcome.
* Internet speed: Standard DSL (at least in the US) is asymmetric, offering a download rate of 1.5 Mbit per second, and an upload rate that is 1/4 to 1/2 of that speed. This may be enough for personal Web pages that are reviewed only a few times a day, but once the hosted site becomes popular, or if there are large files for viewing or download, viewers may experience lags or even failures (time-outs) when they attempt to access the server. It is recommended to set the server to provide zipped files to improve its performance.
* Internet reliability: A binding service level agreement (SLA) is one thing a residential broadband connection does not come with. If the connection is down for a day or two, all one can expect to get is sympathy, a possible apology, and maybe a few dollars refund. There are no provisions for loss of business or revenues. Even under normal conditions, connection speed will at times be slower due to congestion at the local or regional level. That is particularly true of cable Internet, which is shared by all users on the local network. When everyone comes home and starts using the net, the server takes longer to deliver.
* Lack of redundancy: Few homes have redundant Internet connections, or alternative power sources. Using multiple network providers (cable and DSL, or two separate ISPs) is a possible way to get connection redundancy, as long as the providers do not use the same Internet backbone. This also requires configuring the server or router to use two networks, and to have a system in place to alter the IP address when the backup connection kicks in. Installing a UPS is an appropriate solution for short term power-outs, and a generator can provide current during longer periods of power loss. These add breathing time, but are not a perfect solution for long periods of power loss, and may be impractical for some situation (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: The server shares bandwidth with every connected device in the household. When the server gets busy, everyone else waits for Web pages or audio/video streams to download. So, once a site gets popular, be prepared for complaints from all other members of the household. This problem, by the way, is a two way problem as well - when someone in the household is watching YouTube, downloading a large file, or using a peer to peer application (bit-torrent, Skype or other Voice over IP, etc.), the server will be slow. One possible solution is to add a second phone line, dedicated for hosting.
Noise and heat: Any server, and especially the clunker salvaged from disposal to pose as a server, inevitably generates noise from the processor and power supply fans, from the hard drives and from other mechanical storage devices. The constant hum, accented 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 increased load) of the site, may require a fan or air conditioner, unless one plans to use the server room as a sauna. In the summer, especially in hot and humid climates, cooling may be required to keep the server from overheating and possibly even locking up.
* Security of your home network: Unless one uses a physically separate network for hosting, personal computers will share the same network as the server. While a firewall on the router can block access to these machines, the server must be open to the world. Hackers can potentially access your internal network through this server, and get confidential personal information, such as correspondence and financial data. 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.
* No easy upgrade or downgrade options: Unlike hosted servers, there is little option to upgrade or downgrade the system, without incurring additional costs. If a faster pipeline is required (a fractional T1 or a T1 connection is the next step up), we are talking hundreds of dollars in monthly costs, and a possible wait of days or weeks for installation. Upgrading the server means buying a new computer and switching over. With a leased server at a datacenter, scaling up or down is faster and easier, usually a matter of moving a hard drive to a different server for a new monthly fee.
* The buck stops at your desk: When one hosts at home, there is no one else to blame. The host is now responsible 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. Anything goes wrong, the host has to fix it personally, 24 hours a day, 7 days a week, and 365 days a year, which is not as much fun as it sounds. And any 'xplaining to do' is the host's to handle - there is no datacenter to blame...
So, it is better to get the VPS from any reliable web host. I would suggest you with
TuckTail.com this web host provides a top class service at low cost with 24/7 customer support.
