Spring Boot helps you to create Spring-powered, production-grade applications and services with absolute minimum fuss. It takes an opinionated view of the Spring platform so that new and existing users can quickly get to the bits they need.
You can use Spring Boot to create stand-alone Java applications that can be started using java -jar
or more traditional WAR deployments.
We also provide a command line tool that runs Spring scripts.
Our primary goals are:
-
Provide a radically faster and widely accessible getting started experience for all Spring development.
-
Be opinionated, but get out of the way quickly as requirements start to diverge from the defaults.
-
Provide a range of non-functional features common to large classes of projects (for example, embedded servers, security, metrics, health checks, externalized configuration).
-
Absolutely no code generation and no requirement for XML configuration.
The reference documentation includes detailed installation instructions as well as a comprehensive getting started
guide.
Here is a quick teaser of a complete Spring Boot application in Java:
import org.springframework.boot.*;
import org.springframework.boot.autoconfigure.*;
import org.springframework.web.bind.annotation.*;
@RestController
@SpringBootApplication
public class Example {
@RequestMapping("/")
String home() {
return "Hello World!";
}
public static void main(String[] args) {
SpringApplication.run(Example.class, args);
}
}
Are you having trouble with Spring Boot? We want to help!
-
Check the reference documentation, especially the How-to’s — they provide solutions to the most common questions.
-
Learn the Spring basics — Spring Boot builds on many other Spring projects; check the spring.io web-site for a wealth of reference documentation. If you are new to Spring, try one of the guides.
-
If you are upgrading, read the release notes for upgrade instructions and "new and noteworthy" features.
-
Ask a question — we monitor stackoverflow.com for questions tagged with
spring-boot
. You can also chat with the community on Gitter. -
Report bugs with Spring Boot at github.com/spring-projects/spring-boot/issues.
Spring Boot uses GitHub’s integrated issue tracking system to record bugs and feature requests. If you want to raise an issue, please follow the recommendations below:
-
Before you log a bug, please search the issue tracker to see if someone has already reported the problem.
-
If the issue doesn’t already exist, create a new issue.
-
Please provide as much information as possible with the issue report. We like to know the Spring Boot version, operating system, and JVM version you’re using.
-
If you need to paste code or include a stack trace, use Markdown. ``` escapes before and after your text.
-
If possible, try to create a test-case or project that replicates the problem and attach it to the issue.
You don’t need to build from source to use Spring Boot (binaries in repo.spring.io), but if you want to try out the latest and greatest, Spring Boot can be built and published to your local Maven cache using the Gradle wrapper. You also need JDK 1.8.
$ ./gradlew publishToMavenLocal
This will build all of the jars and documentation and publish them to your local Maven cache.
It won’t run any of the tests.
If you want to build everything, use the build
task:
$ ./gradlew build
There are several modules in Spring Boot. Here is a quick overview:
The main library providing features that support the other parts of Spring Boot. These include:
-
The
SpringApplication
class, providing static convenience methods that can be used to write a stand-alone Spring Application. Its sole job is to create and refresh an appropriate SpringApplicationContext
. -
Embedded web applications with a choice of container (Tomcat, Jetty, or Undertow).
-
First class externalized configuration support.
-
Convenience
ApplicationContext
initializers, including support for sensible logging defaults.
Spring Boot can configure large parts of typical applications based on the content of their classpath.
A single @EnableAutoConfiguration
annotation triggers auto-configuration of the Spring context.
Auto-configuration attempts to deduce which beans a user might need. For example, if HSQLDB
is on the classpath, and the user has not configured any database connections, then they probably want an in-memory database to be defined.
Auto-configuration will always back away as the user starts to define their own beans.
Starters are a set of convenient dependency descriptors that you can include in your application.
You get a one-stop-shop for all the Spring and related technology you need without having to hunt through sample code and copy paste loads of dependency descriptors.
For example, if you want to get started using Spring and JPA for database access, include the spring-boot-starter-data-jpa
dependency in your project, and you are good to go.
The Spring command line application compiles and runs Groovy source, allowing you to write the absolute minimum amount of code to get an application running. Spring CLI can also watch files, automatically recompiling and restarting when they change.
Actuator endpoints let you monitor and interact with your application.
Spring Boot Actuator provides the infrastructure required for actuator endpoints.
It contains annotation support for actuator endpoints.
This module provides many endpoints, including the HealthEndpoint
, EnvironmentEndpoint
, BeansEndpoint
, and many more.
This provides auto-configuration for actuator endpoints based on the content of the classpath and a set of properties.
For instance, if Micrometer is on the classpath, it will auto-configure the MetricsEndpoint
.
It contains configuration to expose endpoints over HTTP or JMX.
Just like Spring Boot AutoConfigure, this will back away as the user starts to define their own beans.
This module contains core items and annotations that can be helpful when testing your application.
Like other Spring Boot auto-configuration modules, spring-boot-test-autoconfigure provides auto-configuration for tests based on the classpath. It includes many annotations that can automatically configure a slice of your application that needs to be tested.
Groovy samples for use with the command line application are available in spring-boot-cli/samples.
To run the CLI samples, type spring run <sample>.groovy
from the samples directory.
The spring.io site contains several guides that show how to use Spring Boot step-by-step:
-
Building an Application with Spring Boot is an introductory guide that shows you how to create an application, run it, and add some management services.
-
Building a RESTful Web Service with Spring Boot Actuator is a guide to creating a REST web service and also shows how the server can be configured.
-
Converting a Spring Boot JAR Application to a WAR shows you how to run applications in a web server as a WAR file.
Spring Boot is Open Source software released under the Apache 2.0 license.