Difference between Servlet, Spring MVC and Spring Boot

Do you want to start writing web applications in Java? The first way is to start using a framework (a set of libraries, architectures, design patterns to minimize repetitive code), and one of the popular web frameworks in Java is Spring MVC, which runs under the hood of Spring Boot. Why do you need Spring Boot? First you need to understand the Spring philosophy. There are a lot of libraries under the Spring ecosystem, but not all of them are needed in projects. And they are designed to be connected flexibly without interfering with each other. But over time, when a project has a lot of libraries and code, configuring them becomes a non-trivial task. And I want to take a ready-made template that works well together. Here Spring Boot provides the ability to glue together many Spring libraries easily and simply, in a couple of lines of code or configuration. And under the hood of Spring MVC lies the Servlet API. You can certainly write a web application using only the Servlet API, but the amount of code, especially repetitive code, will be very large. And another developer may not understand this code from a set of spaghetti ifs. To fully understand their difference, I suggest watching the following short video .