just a spring boot configuration tools, integration tools, aids.
springmvc framework, the code is actually running the project
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 ioc and Spring aop, ioc provides dependency injection container, aop-oriented programming to solve the cross-section, and then on the basis of both, to achieve the advanced features extend to other products.
Spring MVC provides a way to loosely couple to develop web applications. It is a Spring module is a web frame. By Dispatcher Servlet, ModelAndView and View Resolver, web application development easy. Problem area is the site should be a program or service development --URL routing, Session, template engine, static Web resources, and so on.
Spring Boot achieve the automatic configuration, reduces the complexity of the project built . It is mainly to solve using the Spring framework requires a lot of configuration problems too much trouble, so it is not used 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).
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.
Summary: the Spring initially use the "factory model" (DI) and the "agency model" (AOP) decoupling the application components. We 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). And then found each development have to write a lot of boilerplate code, in order to streamline workflow, then developed a number of "lazy integration package" (starter), this is the Spring Boot.
So, with the most concise language is summed up:
Spring is an "engine";
Spring Spring MVC is based on a framework MVC;
Spring Boot is based on a set of conditions for rapid development of integrated packages Spring4 registered.
Reprinted; https: //blog.csdn.net/u014590757/article/details/79602309
---------------------
Author: xdyixia
Source: CNBLOGS
Original: https: //www.cnblogs.com/xdyixia/p/9279644.html
Disclaimer: This article author original article, reproduced, please attach Bowen link!
Content analysis By: CSDN, CNBLOG blog articles reprinted a key plug