WCF SOA naming conventions

I have an class library called ServiceLayer which acts as a repository for a ASP.NET MVC application This service layer has a references to a WCF Service called ProfileService which contains Profile methods to perform CRUD operations on a开发者_Go百科 database etc.

I now need to allow mobile devices to communicate with my application so I have created another WCF Service called ProfileService. This service has a reference to the ServiceLayer class library and makes calls to it to undertake Profile operations.

Now this is quite confusing as I now have 2 ProfileServices. The first communicating with my database etc and exposing itself to my service layer. The second communicating with my service layer and exposing itself to mobile devices.

What is the best way to name your services in a SOA environment to avoid confusion of which type is which? especially when mapping between types.

I may also want to create another service which acts as an API to users of the system. What would I name this service ProfileAPI?? I know each ProfileService is in its own namespace but this doesnt help with readability when creating AutoMapperSettings or performing manual mapping.

So if anybody out there knows of a good way to name services in this environment it would be much appreciated.

---

You are looking for a Service Facade

You would end up with a Facade, which is just a specialized interface into your real service. You would define the different services as needed (mobile, users, database)