Hi Everyone, I have been researching standards for Naming of services. Following is the excerpt from Thomas Erl article. Please share your comments/suggestions and any additional resouces on service naming standards.
- The utility-centric context is found in application services involving operations that encapsulate cross-cutting functions, such as event logging, exception handling, or notification. These reusable services need to be labeled according to a specific processing context, agnostic in terms of any particular solution environment. For example, a utility service might be named Notify. - An entity-centric context is established in a business service that represents a specific business entity, such as an invoice or a purchase order. The labeling of entity-centric business services is often predetermined by the entity name. For example, a service may simply be named Invoice or Customer. - Task-centric contexts are required for services modeled to encapsulate process logic. In this case, the thread that ties together the grouped operations is a specific activity being automated by the service logic. Therefore, the use of verbs in service names is common. For example, a task-centric service may be called GetProfile or ProfileRetrieval, if that accurately represents the task's scope. http://www.oracle.com/technology/pub/articles/erl_wsdl.html http://ea.typepad.com/enterprise_abstraction/2006/08/service_naming_.html Thanks, Pavan
