So it isn't really a question :), but welcome everyone! This is a resource so you can ask the questions we haven't thought of. And as we receive ones we haven't answered we will also be writing up tutorials...
To gain the general capacity elasticity you really need to build an application that is designed to use the cloud. Where as this is a virtualized server living in the cloud and in all other regards a normal server (I’ll answer the raw scaling q further down).
The marketing buzz around cloud really makes it seem magic, really it just is an extra layer of hardware protection for most customers. It really only get’s magical if you build an application for the specific cloud layer so that technical limits on server capacity disappear. Or if you need a normal server than changes it’s resources daily/hourly.
So to explain specifically:
It is slightly easier to upgrade in Cloud but since we handle that entire process in either platform it’s not something you can easily see the benefit of. Down the road as we roll out unmanaged vps in both platforms the ability to scale and move around will become more available to clients of course. In most cases that still takes a reboot to upgrade/downgrade a server to a new level just due to limits on that virtualized environment.
So in terms of your specific example, you could upgrade before that rush comes and then downgrade after it’s over. Currently we view that on a monthly basis though and not daily / hourly (we are looking at offering daily/hourly billing though). So in this specific case it would not help you handle that sudden jump any better.
One more thing that is coming down the road is application specific hosting built on the cloud. In that case something like this is possible where you are buying a phpbb application from us and get only access to it and no server level. Then we would design it to really take advantage of the cloud and a cluster of servers. We have no plans currently to develop that for phpbb, but we do for WordPress.
Let me know if you have any questions,
Sure the only different is having your VPS in the Cloud gives it an extra layer of hardware redundancy.
In the cloud if your server has a motherboard failure, ram failure, or similar it would move to a different server in 1 to 10 minutes.
On a normal vps if there was a hardware failure we would need to bring the server down, replace the hardware and get it back up. Plus if the raid array for storage was lost we would need to do a full restoer which would take time (very rare though).
Does that make sense?
Hardware failure is rare already, it just depends if you want to make it ever rarer.
They are included and under the TOS/RUP agreement currently. Shared hosting is a shared environment and no single customer is allowed to use more than their fair share of the server’s resources. We want to make sure that no single user can crash the server or cause problems for the customers. Resource Points take the same rules that have been in place for the last ten years and put them in a simple and easy to use metric for our customers. We rolled out Resource Point graphs ~60 days ago and will continue to expand this feature.
We would never never never upsell our customers on something they don’t need! That is unethical and against every fiber of this company’s culture. We only give recommendations for what your site needs once it grows out of the shared hosting limits.
If you are going over your limit you are using more hardware resources at wholesale cost than you are paying Site5 each month. And that is without paying for the amazing support we provide, software and everything else. Resource Points are not imaginary in anyway and pulled right from Linux process accounting, for a technical description of how they work check out this article: http://kb.site5.com/policies-and-information/resource-points/cpu-time/
Every shared hosting company has a limit, most shared hosting companies use rate limiting and don’t tell you about it. So your site gets lower and lower, and in some cases can serve errors to people once you get too busy. We don’t believe that is the right thing to do, we provide a hard limit so that your webpage serves as fast as possible at all times. But once it hits that limit of fair usage we do alert you and give you optimization guides. If your usage is high enough you might need to upgrade to a higher hosting plan or possibly even a VPS if you have grown out of shared hosting.
Our VPS products where the product is dedicated might be. If you email us we would be happy to analyze and let you know.
We will look at offering an officially HIPAA compliant VPS down the road, but no ETA yet, in the mean time just email us and we are happy to let you know personally depending on your needs,
Also, just a note, you should never need to email us to restart your VPS on our fully managed services. If your VPS has had a problem our team should see the issue, fix it, and email you more details on the problem.
If you ever have to alert us to an issue we have failed, and please let us know so that a manager can look into why the problem wasn’t detected.