Why are the features of springboot adapted to the microservice technology ecosystem?

- Independent Spring application, directly embedded in Tomcat, Jetty or Undertow, runs independently and does not require deployment;

- Provides independent "starter" deployment to simplify Build configuration;

- Automatically configure spring and third-party libraries;

- A certain degree of online environment monitoring;

For the sake of independence, springboot directly integrates web services in In the framework, after the project is created, it can be started directly as a microservice. This method saves the deployment process. The development and deployment of the past model is not only troublesome, but also cannot even be deployed for self-test in some scenarios. Springboot's development and deployment are integrated and self-testing. Test delivery is a matter of course, each module is more independent, and it is very convenient to cooperate with the agile development process.

springboot uses starter to encapsulate its own extended functions and comes with default configuration. The required functions only need to introduce the corresponding starter. If you want to print logs, there is spring-boot-starter-logging. If you want a database, There is spring-boot-starter-jdbc for access, spring-boot-starter-security for password verification, and spring-boot-starter-actuator for monitoring. Springboot itself is lightweight enough. With the rich functional expansion of starter, using springboot to develop the simplest services to the most complex services can be easily constructed, which is very nice.

Springboot's automatic configuration, @EnableAutoConfiguration can use the characteristics of SpringFactoriesLoader to summarize and load the JavaConfig classes marked with @Configuration into the final ApplicationContext. Based on the conditions preset by @Conditional, the automatically configured dependent modules are on-demand Loaded, these dependent modules will only take effect if they meet certain specific conditions. The above content belongs to the school bag. Let me explain again. The automatic configuration uses the characteristics of SpringFactoriesLoader to find the configuration class. After filtering and summarizing, it is loaded into the IOC container together.

By referencing the function of spring-boot-starter-actuator, you can obtain system information when the springboot system is running, such as obtaining basic application information, health checks, performance indicators, etc. But usually, a tripartite framework is used to solve production monitoring problems, which can provide more and more complete monitoring functions.

The design of springboot greatly reduces the workload of programmers in building projects. It is easy to create a project and make extensive use of spring's custom configuration. It can run well even without modifying any configuration. When the era of microservices arrives, services are often online and offline in a short period of time. Springboot's rapid construction and deployment characteristics, relying on the huge Java ecosystem, make it popular rapidly.

Related recommendations: "java video tutorial"

The above is the detailed content of Why are the features of springboot adapted to the microservice technology ecosystem?. For more information, please follow other related articles on the PHP Chinese website!