Introduction to Spring Boot
Learn what Spring Boot is, why it exists, and how it lets you build production-ready Spring applications with almost no configuration.
Introduction
If you have ever tried to build a Java web application using plain Spring Framework, you know the drill: you configure a `DispatcherServlet`, wire up an XML or Java-based application context, add a servlet container like Tomcat, and only then start writing actual business logic. Spring Boot was created to remove almost all of that ceremony. It lets you go from an empty folder to a running, production-ready web application in minutes, not hours.
- What Spring Boot is and the problem it solves.
- How auto-configuration reduces boilerplate.
- What a minimal Spring Boot application looks like.
- The core features that make Spring Boot popular.
What is Spring Boot?
Spring Boot is an extension of the Spring Framework that simplifies the process of creating stand-alone, production-grade Spring applications. In one sentence: Spring Boot looks at what libraries (JARs) are on your classpath and automatically configures sensible default beans for you, so you do not have to write that configuration yourself. This single idea, called auto-configuration, is the heart of everything Spring Boot does.
Instead of assembling a web application piece by piece, Spring Boot ships with an embedded web server (Tomcat by default), sensible default settings, and a set of "starter" dependencies that pull in everything a common use case needs. You add the `spring-boot-starter-web` dependency, write one class, and you already have a working HTTP server.
A Minimal Spring Boot App
Every Spring Boot application starts with a single class annotated with `@SpringBootApplication`. This one annotation combines three separate annotations (`@Configuration`, `@EnableAutoConfiguration`, and `@ComponentScan`) into a single, convenient entry point.
package com.programinds.demo;
import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;
@SpringBootApplicationpublic class DemoApplication {
public static void main(String[] args) { SpringApplication.run(DemoApplication.class, args); }}Click Run to see what this code prints.
That is the entire application. Running this single file starts an embedded Tomcat server on port 8080. No `web.xml`, no external application server installation, no manual bean wiring — Spring Boot inspected the classpath, saw the web starter, and configured a working web server for you automatically.
Key Features
Auto-Configuration
Automatically configures beans based on the JARs present on the classpath, removing most manual setup.
Embedded Servers
Ships with embedded Tomcat, Jetty, or Undertow so you can run "java -jar" without installing a separate server.
Starter Dependencies
Curated dependency bundles like spring-boot-starter-web pull in everything a use case typically needs.
Production-Ready
Includes Actuator for health checks, metrics, and monitoring out of the box.
Common Mistakes
- Thinking Spring Boot is a separate framework from Spring — it is built directly on top of Spring Framework.
- Forgetting that `@SpringBootApplication` must sit on a class in (or above) the package where your other components live, since it triggers component scanning from that package downward.
- Assuming auto-configuration is "magic" that cannot be overridden — any bean you define yourself takes precedence over the auto-configured default.
Best Practices
- Place your main application class in the root package so component scanning covers your whole codebase.
- Use Spring Initializr to generate new projects rather than hand-assembling the build file.
- Read the console startup log at least once — it tells you exactly which auto-configurations were applied.
- Keep the main class focused only on bootstrapping; put actual logic in separate components, services, and controllers.
Frequently Asked Questions
No. Spring Boot is built on top of Spring Framework. It does not replace Spring's core concepts (dependency injection, beans, the application context) — it just removes the manual configuration needed to use them.
No. Spring Boot embeds a web server (Tomcat by default) directly inside your application JAR, so "java -jar app.jar" is enough to run it.
No. While it is extremely popular for building REST APIs and web apps, Spring Boot also works for batch jobs, messaging applications, and plain command-line tools.
Key Takeaways
- Spring Boot is built on top of Spring Framework, not a replacement for it.
- Auto-configuration inspects the classpath and configures sensible default beans automatically.
- `@SpringBootApplication` combines `@Configuration`, `@EnableAutoConfiguration`, and `@ComponentScan`.
- Spring Boot embeds a web server, so applications run as standalone JARs.
Summary
Spring Boot takes the power of the Spring Framework and removes almost all the manual setup that used to stand between you and a running application. With a single class and a few dependencies, you get a fully working, production-ready web server. Next, you will look at the history of Spring Boot and understand exactly what problems it was created to solve.