How to name an Application Service?

[Alan Prochaska]

How do you all name your Application Service CIs?  

Do you have a naming standard that works?  

Anyone care to share or hold forth?

In our young implementation, Application Services primarily represent deployments of the application.  Someone decided to name the App Services "<bus app name> + <deployment type> + <version>".  This leads to long and clunky names.  For analytic or machine access it's easier to get deployment type and version from metadata, however, humans get confused and frustrated having multiple objects in the same class with the same name (distinguished by other meta data).

What do all of you do?  How do you name your app services?  And does it work effectively?

Thanks for feedback, thoughts, and stories.

Alan Prochaska

Kaiser Permanente

[CMDB Whisperer]

While I can see how that certainly makes it easy to reproduce, the down side of that is that Technical and Business Services and Offerings are not necessarily built around an Application focus.  Rather, services should be focused on the outcomes that are delivered, and the offerings should be focused on how those outcomes are delivered -- which may or may not be centered on the Application that is used to deliver the outcomes.  Bottom line is that this naming convention may impede your service definition or bias it in a way that could have you rethinking things down the road.  Caveat emptor.