Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

The other obvious - it potentially makes your server management much easier, particularly if you need a lot of computing power, or lots of servers quickly.


sort by: page size:

The shortest explanation would be:

These will allow you to automatically scale up or down easily. You don't have to maintain your server.

It has its advantages and disadvantages.


Basically, it allows you to requisition servers more quickly by providing a baseline system. If you're not doing scalable-on-demand work (and most of us aren't), it's not that useful.

Also automatic autoscaling and it can be cheaper since you utilize basically all of your billed Compute instead of overprivisioning server capacity.

It allows you to run multiple servers (e.g. NFS + git + MySQL + Apache) without worrying so much about memory footprint.

The big one is convenience: if you need to do some quick maintenance from a computer you're not usually using, it's fast and easy to do so here (e.g. if you want to administer your server from a firewalled work PC, or from your parents' house).

More dynamic, better management, dead easy to get distributed programs in multiple machines.

It allows for easy live migrations for maintenance, and allows us to build VMs that are happily 100% oblivious of the underlying hardware. While most of our servers are split into multiple VMs, we consistently deploy new hardware with VMs even if they're intended for a single function simply because of consistency and ease of maintenance.

For one, you can use your compute resources much more elasticly. You can create and delete VMs on demand and don't need to drive to the colo to reimage.

And allows you more flexibility with caching and load balancing too.

It makes setting up a home server much easier, because you can get infinite free static IPs.

That doesn't contradict that "most users" don't benefit, though.


1) They let you be more fine-grained. Not all services need a full VM (even one of the small ones).

2) They let you have burstable instances, but controlling all the services sharing those resources, rather than being subjected to unknown neighbours.

3) Related to the previous points, they let you take advantage of free resources by distributing batch operations over VMs not under peak capacity.


Lower overhead, and full integration with the host filesystem I believe are the 2 primary reasons many use it

They make shared folders and individual files a lot easier than VMs, also process monitoring from the "host".

My impression is that it makes deploying your 100th server much easier, at the cost of making your first several much harder. If you're going to have 100+ servers, that's probably worth it. If you're not (and most companies aren't), then it's like getting your CDL so that you can go to the grocery store in a semi-tractor trailer, when you should have driven there in a compact car.

One benefit is that you can run it on your existing IIS cluster where you already run yor stuff.

In short - faster, easier on ram usage and easier to configure.

Mostly automatic DNS management and it being more easy to use more than one machine for things.

Probably makes full disk encryption easier. Also compared to how much memory you can have on a modern server - it's trivial amount

You pay upfront for some more components. In exchange, you get a lot of benefits.

'classic' servers are only simpler if you can postpone dealing with their complexity.

next

Legal | privacy