Admittedly my internal product names are contrived, but as coders and what not, we are exports
at the TLA. So in daily use it would probably reduce to sls, and sle with some versioning tagged
on to the end. And as for say this to marketing, they can have there own external name, they
don't really need to know the internal one do they, since there going to be changing it all the
As for the servers, I've figured out where you and i differ. One of the things I do when wearing
my sysadmin hat as opposed to my developer hat, is PCI-DSS compliance for a payment
gateway. If you haven't done it, just know that it tedious to an extreme, but over all a good thing.
One of the things that it bring to the table, is that every service lives on a different server, to
minimize exposer from external threats. This is why we had an explosion in the number of
servers, but has enabled us to have a 1 to 1 service to server name based infrastructure.
Obviously no one is going to throw real hardware at a lot of these services, so most are handled
with virtualization. But each of those servers is named for its function as well which HBS-1 or
whatever. Combined with the Fibre channel LUN that one service/server or another is stored on.
Needless to say, we have a lot of infrastructure to manage, and it's all pool based. So the need
and the ability to name things according to service makes all of this manageable. Right now, I
manage 120+ servers, so it's all about manageability.
I guess it's an apples to oranges kinda thing, in that I would not run the mail server, file server,
and other things on the same box, but that's a luxury I have and other may not.