Search code examples
asp.netwcfdesign-patternsseparation-of-concernsmvp

How do I separate business logic and database calls from a WCF web service?


This question may have been asked before, but I'm looking for a different answer than what I've seen.

Our website is in ASP.NET and we use the model-view-presenter pattern to get business logic out of the markup codebehind.

Is there an accepted pattern for web services for getting business logic out of the codebehind? It seems like putting the logic in a 'presenter' is misleading since the calls don't really present anything to the user, and may not even send back data to the client.


Solution

  • I ended up going with a 'presenter' type pattern like I was for my ASP.NET pages.