title: Business Logic on ASPNet MVC outside of Model
body: <p>I have been working with asp.net core web api for the past few days, I am familiar with MVC and SOC etc but I got confused a bit with the core mvc tutorials.
  So in all the tutorials (to keep them simple) they put the business logic inside the Controller, but this is ofcourse not compliant to MVC. </p>
  
  <p>In general I have created:</p>
  
  <ul>
  <li>Model (to create the DB structure through EF)</li>
  <li>Controller (to serve the endpoints and act)</li>
  <li>Repositories (to provide the query logic to the DB)</li>
  </ul>
  
  <p>Now I am bit confused with Services and also where am I supposed to put the business logic? I mean the Model is one place, but I dont want my controller to access the model directly but more like a Facade/Factory. 
  How do we achieve this in aspnet?</p>
  
  <p>You can find my working repo at <a href="https://github.com/drakoumel/DatacircleAPI" rel="nofollow">https://github.com/drakoumel/DatacircleAPI</a></p>
  
  <p>I hope that after I can get a good explanation of this, to write it in the documentation of stackoverflow to help others.</p>