title: Spring MVC and Web Application Architecture
body: <p>My understanding of Spring MVC is that the View layer is responsible for the user interface that is populated with data, the Model represents a Map of values made available to the View Layer, and the Controller controls how and what data is passed to the Model as well as what business logic is carried out.  The "business logic" can be divided into one or more other layers - generally a Service layer and/or Data Access layer.  Is this correct?</p>
  
  <p>I've seen other explanations for the MVC pattern where the Model is considered a layer with Entities, Data Access Objects, and Services.  The View is responsible for the user interface.  And the Controller is the gateway between the two.  I don't think this applies to Spring MVC and other implementations of MVC for web frameworks.</p>