Author: Qianlongwuyong
Spring framework is like a family, there are a number of derivative products such as boot, security, jpa, and so on. But they are the basis of the Spring aop ioc ioc and provides dependency injection container aop, to solve the cross-section oriented programming, and then on the basis of both, to achieve the advanced features extend to other products.
Spring MVC MVC framework is based on a major problem Servlet WEB development, because the Spring configuration is very complex, a variety of XML, JavaConfig, hin process more cumbersome. So in order to simplify the use of the developer, thus creatively introduced Spring boot, convention over configuration, the spring simplifies the configuration process.
Some put it more simple: Spring initially using the "factory model" (DI) and the "agency model" (AOP) decoupling the application components. I feel very good use, so in this mode out a MVC framework (Spring with some of decoupling components), with the development of web applications (SpringMVC). Then there are found each time to write a lot of boilerplate code development, in order to streamline workflow, then developed a number of "lazy integration package" (starter), this is the Spring Boot.
Spring MVC functionality
Spring MVC provides a way to loosely couple to develop web applications.
Spring Spring MVC is a module of a web-type frame. By Dispatcher Servlet, ModelAndView and View Resolver, web application development easy. To solve the problem areas is the site of application or service development --URL routing, Session, template engine, static Web resources, and so on.
Spring Boot function
Spring Boot achieve the automatic configuration, reduces the complexity of the project built.
As we all know the Spring framework requires a lot of configuration, Spring Boot introduced the concept of automatic configuration, so that the project settings easy. Spring Boot itself does not provide the core features and extended functionality of the Spring framework, but for quick, agile develop a new generation of applications based on the Spring Framework.
That is, it is not intended to replace the Spring approach, but the Spring framework and closely integrated tools for lifting Spring developer experience. At the same time it integrates a large number of third-party libraries common configuration (e.g. Jackson, JDBC, Mongo, Redis, Mail , etc.), Spring Boot application of these third-party libraries almost zero configuration of the box (out-of-the- box), most of the Spring Boot application only requires a very small amount of configuration code, developers can focus more on business logic.
Spring Boot just bearers assist you simplify the process of building the project. If the carrier is WEB project, using as Spring MVC MVC framework, it is exactly the same as described above you and workflow, because this part of the work is done rather than Spring MVC Spring Boot. 
For the user, after switching to Spring Boot, project initialization methods have changed, the profile has changed, the other is no need to install a separate Tomcat server such containers, maven jar packets directly run up play is a website, but you most core business logic and business processes without any change.
So, with the most concise language is summed up:
Spring is the "engine";
Spring MVC is based on a Spring MVC framework;
Spring is based on the Boot condition Spring4 registered a rapid development of integrated package.
Welcome to share with everyone, like articles like this one point to remember, thanks for the support!