Winner winner, chicken dinner. As someone who is still managing pets, I even still prefer a standardized naming scheme. I use: ${project}-${dev/staging/web}-

Winner winner, chicken dinner. As someone who is still managing pets, I even still prefer a standardized naming scheme. I use: ${project}-${dev/staging/web}-${web/db} (which so far has covered my bases, I'm sure you can come up with any logical extensions if you are running load-balancers or other types of servers, add a number if you are running multiple frontends or clustered DBs, etc) Even as someone who manages pets, I can't tell you how much time this has saved me from having to look up server names. I have done the generic "assign everything to a single machine## sequence" and it sucks ass. Was your production web server for this app machine32 or machine 54? What about the staging server? Can't even imagine the hassle of uuids as server names. (of course so far I have done the pets thing in my internal network... but I can tell you that my father with a 40y career in managing servers for major corporations uses names like vmhost01/fsrv01/tvpc at home... which tells you what he thinks of that.)