title: Repository pattern with business logic
body: <p>I just have the intention to write demo application based on DDD. My repository uses Entity Framework ORM an everything is great. MVC and Windows Forms applications calls repository methods and that works. But What If I decide to replace Entity Framework with Dapper or NHibernate or my data comes through web service? I konw that I need to rewrite repostiory implementation, but what with my bussines logic. Business logic now is placed in Repository. Some examples have business logic in controller but I have more than one client.  Do I need to put some layer above Repository? What is the name of that layer in concept of DDD.</p>