Technical Advice - Choosing a Virtual Private Server

If your website is currently hosted on a shared account and is growing rapidly, you might want to consider a Virtual Private Server hosting option.
With shared hosting environments proving to be unstable for sites with sudden high traffic, a virtual private server gives you more flexibility and resources.
With a Virtual Private Server you are guaranteed these resources. You don't have to be worried about taking up too many resources, or someone else taking those resources and slowing your website down. You also have the ability to customize the server environment to your websites needs without having the limitations of a shared account.

Could any other useful information be added??

That's a great summary!

Just to add:

1) If anyone is thinking of cloud hosting then forget it... In my experience despite all of the BS spin that its super awesome etc - its very volatile with performance being like a yo-yo... and its dependent on other sites and availability of resources... So for me my vote goes for VPS before entering into to the option of dedicated hosting.. Curious to hear of further opinions on that... As you can tell I'm no longer experimenting with cloud hosting and want nothing to do with it due to the damn headaches it has caused....

2) If you're going for VPS - I would recommend that it includes cPanel together with adequate support agreement from the provider... I've seen some providers whereby the VPS offer looks really cheap then you take in account of additional cPanel license costs and managed support and suddenly its way too expensive lol.... Some providers I've seen state for 1 hour support it costs $200 - so keep that in mind if you opt for unmanaged support - plus you'll be responsible for server upgrades etc...

So unless you know what you're doing go for managed support... and make sure to do your home work as to reviews regarding their support response times/service level agreements etc..

Nice write up DDSvpsHost.

I will only disagree with one point.

DDSvpsHost said:

With shared hosting environments proving to be unstable for sites with sudden high traffic, a virtual private server gives you more flexibility and resources.

Click to expand...

This statement is both true and false, depending upon the situation. A high traffic site should not rely on shared hosting where you have shared resources. A VPS does give you dedicated resources (if it is XEN or KVM, not OpenVZ).
However, a VPS gives you a finite number of resources, based on the plan you choose. Where as shared hosting has the entire servers resources, shared between the users on the server. Depending upon what plan you choose, how the host has resource limits set, and other loads on the server, a shared hosting account could be able to use 2GB of RAM, which would outperform a 1GB RAM VPS.

The biggest benefit to VPS's is the dedicated resources (so that your site is not affected by other users using too many resources) and the greater access to and control over the virtual server (root access). Another benefit to VPS's is that their instantly scalable. If you order Plan "A", and decide you need more resources, tell your host you want Plan "B", pay the fee, your host clicks a few buttons, and you have the added resources.

But, that is not done instantly or automatically "for sites with sudden high traffic". The only way to be instantly scalable is to have Cloud hosting.

elcidofaguy said:

1) If anyone is thinking of cloud hosting then forget it... In my experience despite all of the BS spin that its super awesome etc - its very volatile with performance being like a yo-yo... and its dependent on other sites and availability of resources...

Click to expand...

Very true. There are benefit to cloud hosting, but there are some major draw backs too:

Pros
Instantly scalable - If you get that sudden flood of traffic, your resources will grow instantly to handle the added load. (up to the limits of the cloud infrastructure)
Distributed computing - By definition, cloud hosting should use multiple server, preferably geographically divers. This way if one physical machine goes offline, the other servers pickup the extra load and everything stays online.

Cons
Pain in the butt to deal with - Cloud hosting is not as simple as signing up for an account and uploading your site.
May not be any better uptime - Too many people think that cloud hosting automatically means your site will be up 100% of the time. It doesn't. Even Amazon AWS experiences downtime.
May not be any more secure - After all, it is still shared hosting, with a few extra features
Can be VERY Expensive - With Cloud hosting, your billed for what you use. If your site uses a little this month, you may get a bill for $20. If a Facebook post goes viral and your site traffic explodes, you may get a bill for $2,000 next month.


Also keep in mind, I have seen some providers offering shared hosting, and call it "cloud hosting" as a purely marketing gimmick. If you decide you want to try cloud hosting yourself, make sure you ask questions to find out what your really getting!

I'll like to add that if you're looking to run websites on your VPS, cPanel is a popular and user friendly control panel, but it is by no means the only good option. There are free control panels out there, such as Vestacp, that practically has the same functions. It's user friendly and it's free. This can save you $15 in cPanel license costs.

Most people often stick to what they know since switching might seem time-consuming, so it's important to find a hosting provider that can simply explain how everything works on the new interface.

you need minimum 1024MB for cPanel right. Now if you are using ngix against big traffic. I could say uninstall the cpanel bcz either cpanel or ngix. your VPS is cool as long as you have a small site to operate. cPanel can put load on your cpu and make your site most slower so if you have good resourced VPS then use cpanel and try to stick wi8th it. It's not only do the simplify the work it's also speed up on your work..

Everything else depends on you.

Moving from a shared hosting properly managed to a small vps with a control panel... I'm not sure it's a real solution.

If the resources of a vps are more "dedicated" than on a shared hosting, it's true only if you don't use them for running the control panel. Under 8-12GB RAM and at least 4vCPU, it will just slow down the vps. Most of premium control panel (cPanel, Plesk, DirectAdmin) are ready to manage up to 300 websites in dedicated servers. The main purpose of a control panel is to manage huge amount of domains and to do the best it possible.

But if you take a vps for yourself, try to manage it using ssh. It will cost less, and you will run your websites 2x-3x times faster. Many VPS providers have LAMP/LEMP stack ready to go. And if it take time to setup, just write a bash script when doing it. So you will be able to do it in few seconds next time.

Keep in mind you will be happy to use a control panel when you will have more than 10-15+ websites to manage. But if you want performance and ability to customize your server, just learn how to setup it. There are so many good websites to learn : howtoforge, oceandigital, github.

Or if you really don't want to use ssh, try a remote panel like serverpilot.io. The best alternative to avoid using resources for nothing.