title: Why is concept of Model and Controller intermingled in Angular.JS?
body: <p>I am very new to Angular world and I have mostly worked with .NET MVC architecture where there is a clear delineation between entities like <strong>Model and Controller</strong>.</p>
  
  <p>It is as clear as following in my opinion:</p>
  
  <ul>
  <li>A Model is container of data</li>
  <li>A controller is basically collection of the functions which handle the interaction between business and View on the client side</li>
  </ul>
  
  <p>They are two separate files and two separate types. There is no way someone can confuse between a asp.net view and asp.net Controller</p>
  
  <p>However, in Angular world(which is apparently a MVC architecture), a controller looks like something described at following link:</p>
  
  <p><a href="https://scotch.io/tutorials/making-skinny-angularjs-controllers" rel="nofollow">https://scotch.io/tutorials/making-skinny-angularjs-controllers</a></p>
  
  <p>To me, by .NET standards, this is a hybrid of Model and Controller because it not only carries data (<strong>like model</strong>) but also carries functions**(<strong>Just like Controller</strong>)**. Not only that, model is actually part of Controller.</p>
  
  <p>My question is that if a model in Angular looks like the one described in the link above, what does a model look like by itself?</p>