VPS vs. VPS Cloud

Neoon

@randvegeta said:

@Neoon said:
VPS = Cloud

But if you put Cloud into the name, that makes you able to charge more for the same shit.

Its like putting gaming into computer stuff.

Does that mean you can sell a Gaming Cloud for even more? What about Blockchain Gaming Cloud?

Or we could use the same conventions that Gillette use for their razors, and add the words 'Stealth' and 'Fusion' to the names.

Fusion Stealth Blockchain Gaming Cloud Server - Only $99 /month!

Blockchain for JPEG, as bad as it sounds, its not a joke.

hostixs

It can vary a little from provider to provider but generally it means that the infrastructure is virtualized and runs on a cluster. I.e. your server isn't tied to a specific piece of hardware and, should the hardware running the server that hosts your site have issues, the server would come back online on another piece of hardware.

There are those that sell shared cloud hosting - where in it's shared hosting on cloud infrastructure. There are those that sell VPS on the cloud - being that it's a VPS on cloud infrastructure. And then those that sell the cloud directly - generally this is Infrastructure as a Service [IaaS] in most cases.

Due to the nature of the cloud / clustered setups usually storage is either centralized and fault-tolerant or distributed and self-healing. There are a lot of viable technologies out there for both from a high-end all-flash-array SAN to something like EMC XtremeIO or even StorPool, Ceph, etc.

geshoto

@HostDoc said:
Depends on how the provider is trying to market their services.

For me and in relation to the products our company offers;

A VPS is a standard virtual machine with exactly the same capabilities as a cloud VPS except versatility. A VPS has no flexibility and you are stuck with the one VPS and its configured specs for the life of that VPS. You could migrate the VPS to a node in a different location and most probably pay a fee but will still have limitations such as having to cancel your plan and purchase a new one if you wanted a smaller plan or wanted to make changes effortlessly.

A cloud VPS gives you flexibility as well as choice. With a cloud VPS, you can create and destroy your VPS on demand, and can provision it in any available location that your provider has.

You can give your VPS as much or as little resources as it needs and replicate that same VPS or make different VPS' for different uses in other locations.

Once a project is finished with a particular VPS, you can destroy it and spin up another one on demand. You can create HA infrastructures, your own personal CDN's, DNS, etc without the need of cancelling plans to get bigger or smaller one's or having so many machines idling.

This is incorrect, with KVM and Xen you can quite easily add extra resources to a VPS, including CPU cores RAM and extra storage with a simple reboot.
That is the entire point of a VPS and using virtualized infrastructure, otherwise people would just put everything on bare metal servers.

It would be handy if a few of you got some experience with what you are talking about before giving advice on a public forum.

HostDoc

@geshoto said:

@HostDoc said:
Depends on how the provider is trying to market their services.

For me and in relation to the products our company offers;

A VPS is a standard virtual machine with exactly the same capabilities as a cloud VPS except versatility. A VPS has no flexibility and you are stuck with the one VPS and its configured specs for the life of that VPS. You could migrate the VPS to a node in a different location and most probably pay a fee but will still have limitations such as having to cancel your plan and purchase a new one if you wanted a smaller plan or wanted to make changes effortlessly.

A cloud VPS gives you flexibility as well as choice. With a cloud VPS, you can create and destroy your VPS on demand, and can provision it in any available location that your provider has.

You can give your VPS as much or as little resources as it needs and replicate that same VPS or make different VPS' for different uses in other locations.

Once a project is finished with a particular VPS, you can destroy it and spin up another one on demand. You can create HA infrastructures, your own personal CDN's, DNS, etc without the need of cancelling plans to get bigger or smaller one's or having so many machines idling.

This is incorrect, with KVM and Xen you can quite easily add extra resources to a VPS, including CPU cores RAM and extra storage with a simple reboot.
That is the entire point of a VPS and using virtualized infrastructure, otherwise people would just put everything on bare metal servers.

It would be handy if a few of you got some experience with what you are talking about before giving advice on a public forum.

I did not mention anything about problems upgrading but rather the issue with shrinking the disk or downgrading which is actually not as easy as one might think and could result in data loss.

Maybe, learn to read the contents properly before making pointless comments.

DETio

HostDoc said: I did not mention anything about problems upgrading but rather the issue with shrinking the disk or downgrading which is actually not as easy as one might think and could result in data loss.

Maybe, learn to read the contents properly before making pointless comments.

KVM Actually technically supports Shrinking Disks / Elastic Disks - using Thin Provisioning - it's just not common for some 'VPS' panels to have that supported.

If you use Thin Provisioning you can easily lower the size of total storage and the storage works exactly like OpenVZ (Where the Host's Disks only gets used up when the VMs use up the disk). One downside is slightly lower performance - so every option has it's benefits/drawbacks.

budi1413

vps - on earth | vps cloud - on sky

obviously.

jure12

@budi1413 said:
vps - on earth | vps cloud - on sky

obviously.

It seems to me all the same.