it allows us to focus on developing the application, already leaving most of the configurations ready or extremely simplified for us developers. Spring Framework
embedded server, a "starter" where we can choose the initial dependencies of the application, health check of the application, without the need to configure several dependencies via XML. Spring Boot
basis for your application to run, through Spring Security we can easily add authentication to our application and connect and query the database with almost no configuration through Spring data Web Apps
the already known and widely used Spring MVC (servlet), having as main difference the support for reactive NIO streams and for supporting the concept of backpressure with the Netty server coming by default embedded in its architecture. spring webflux
reactive part in addition to the Servlet structure that already existed, each module of these is optional, you can use the Servlet part, the reactive part or even both in your applications. spring webflux
API that was used independently of the execution time and in a non-blocking way, which was possible with the servers (Netty for example) that consolidated themselves in the asynchronous and non- blocking operation. spring webflux