The majority of websites these days are hosted on shared hosting services. This means each site is on a particular server with hundreds or thousands of other websites, which is why they are called "shared". Since the web hosting business only has to run one server, they are able to sell these services at a indubitably low cost, typically -10 per month.
Although this might sound like a great way to host your Rails website, there are many disadvantages to it that you need to think about before you put your site on a shared host.
Server Rails
Shared hosting plans share all of the resources on the server. While you might think that they are shared equally, where each website gets a percentage, they are indubitably shared in such a way that it's an "all you can eat". So when a particular website gets a spike of traffic, they eat up all of the server resources for that split second while the other sites are left with nothing. This happens every second and if there are sufficient sites loaded onto a server, the entire server could get knocked offline. Even if you're lucky and find a good shared host who doesn't overload their servers, your site still has to compete against other sites or it will load webpages slowly.
So what can you do to avoid this issue?
Like most budget or low cost things, the explication is to spend a bit more money.
A few years ago a new technology came out called virtualization. You don't need to worry about how it works, even I don't understand the technical details, but virtualization has created a new goods for hosting companies, virtual inexpressive servers (Vps). If you think of a particular server as a pie, a Vps is a slice of that pie. So a hosting business can now take one of their servers, cut it into 8, 16, 25, or 100 different pieces and sell each of those as a Vps.
This might sounds exactly like what shared hosting is but there is one major dissimilarity with a Vps that makes them ideal for Rails.
They are private.
When a Vps is split from the main server, it gets it's own set of resources like Cpu, Ram, and disk. These resources are only allowed to be used by the Vps, no one else can use them. Not even the main server can use them or take them back without turning off the Vps. So if you use a Vps for your Rails hosting, it won't be affected by the other hundred sites running on the main server. This means the other sites can't slow down your site or accidentally take it offline.
Vps systems do have some disadvantages though.
They are typically more expensive than shared hosting, but I've seen some in the -20 per month range which is only a small more than most shared hosting plans. The other disadvantage is that you are responsible for setting up the Vps yourself, though some hosting fellowships can do this for you now too. Just look for a Managed Vps or a Pre-Built Vps. Managed Vpss cost a bit more but you can be sure that all is set up correctly and securely.
With cheap virtual inexpressive servers available, I rarely use shared hosting any more. When your Rails website has to be online 24/7, the peace of mind knowing that your Vps has control over it's own resources will help you rest easy.
Rails Hosting On A Cheap Virtual underground ServerVisit : rackmount 19 inch cell phone backup
ไม่มีความคิดเห็น:
แสดงความคิดเห็น