title: Is Repository Pattern with Domain Driven Design become Anti-Pattern?
body: <p>First of all I want to clarify that I am new to Domain Driven Design and I am asking this question because I have read something called Anemic Domain Model.</p>
  
  <p>Most of the time I see following thing while working with Repository pattern.</p>
  
  <ol>
  <li>We have One Generic Repository</li>
  <li>We have Model that only contain set of public properties but it does not contain any method ( So It become Anemic Domain Model as per definition of DDD) because here repository class handle other process for that entity or model.</li>
  </ol>
  
  <p>Please provide your valuable answer for my query.</p>
  
  <p>Let me clarify few things.</p>
  
  <p>Generic Repository means Generic interface that get implemented by Entity repository.</p>
  
  <p>My confusion is regarding following thing</p>
  
  <p>For example: 
     Suppose I want to save </p>
  
  <pre class="lang-cs prettyprint-override"><code>    public class User
      {
          public int Id { get; set;}
          public string Name { get; set};
      }
  
      public class UserRepository : IRepository&lt;User&gt;  
      {  
          // All Operation Like Save / Get /  UserEntity (Domain Object)       
      }
  </code></pre>
  
  <p>So here is my User class do nothing instead it just have properties and other operation handle by <code>UserRespository</code>. So my User is Anemic Domain model. ( As it do nothing specific) </p>
  
  <p>Here in attached image I consider <code>ProductRepository</code> so my question is: Is My Product class an Anemic model?</p>
  
  <p>Please consider following Sample Image for what I am trying to say.</p>
  
  <p><a href="https://i.stack.imgur.com/31XbB.png" rel="noreferrer"><img src="https://i.stack.imgur.com/31XbB.png" alt="enter image description here"></a></p>