I'm writing a WCF service application where I have isolated the WCF classes into their own "Presentation Layer" (For lack of a better term). Then underneath that, I have an application layer that orchestrates the domain objects.
I like the fact that none of the WCF technology has leaked into the application layer so I can easily swap it for something like Web API (Which I've considered). My concern is, however, that it seems to break the don't repeat yourself rule. The WCF layer has essentially become a "Proxy" layer that just hands off calls to the application layer, maintaining the same signatures.
For example:
public void Method(string arg)
{
_appService.Method(arg);
}
Is this over kill? Should I just move the logic up into the WCF classes?