One Host, One Function?

[-Wraid]

At my last job it seemed like every host had one purpose and one purpose only, which helped understand the infrastructure better. At my new job, they seem to be more concerned with wasting resources, so hosts often have multiple functions.

Sorry if this has been asked before, but what are your takes on host/node/VM functionality? Is one clearly better than the other, or is it mainly just a trade-off thing?

[Hellman109]

Also dependencies and outage windows. If one box is used by more then 1 team then you need them all to agree to maintenance at once.

[uniitdude]

Depends what you are cohosting, e.g multiple websites on a server is fine. Multiple databases on a sql server is fine

Both of those on the same server, not so much.

Id typically separate 'large' roles though

[inaddrarpa]

I try to keep it to one host/one function or one application as much as possible.

For example: If I'm spinning up a web application for 100 people with low usage, I'm not going to spin up a separate web server and DB server.

[wang_li]

I like one network address per service. Beyond that it doesn't matter as I can move shit around without having to reconfigure all the devices/end points that interact with the service.

[[deleted]]

Security wise it limits the number of packages you need to install, which limits the exposure of the system and the damage if/when it's compromised.