Gain insights into Spring Boot, delve into auto-configuration, database integration, and web services, and learn to build a functional "Elite Club" web application.

Microservices with Spring Boot_Convert MBE Hacking with Spring Boot 2.3 Reactive Edition.png

spring_lessons_v5_gitclone_tarball.tar.gz

Spring Boot Billionaire Club

EliteClubJob

EliteClubJob_springdata

EliteClubJob_searchclub

EliteClubJob_searchrestclub

Spring Boot Billionaire Club forbes400

EliteClubJob-jetty-7070

SpringBillionaireClub

In this course, you will cover the most important aspects of Spring Boot including auto-configuration, database integration, and webservices.

Throughout this course, you will build a fully functional application called the “Elite Club” which any browser can connect to. The initial version of the application will expose one rest endpoint to return the hardcoded list of elite clubs. The subsequent chapter will be improving the application by adding new features.

By the end of this course, you will be well equipped to build enterprise and web applications.

Building Enterprise Applications with Spring Boot

# Auto-configuration report
Upon starting the application, we don’t get a lot of information of how Spring Boot decided to compose our applications through auto-configuration.

For debugging purposes, it’s essential to know which auto-configurations are applied to the application.

The following are three ways in which Spring Boot generates the auto-configuration report.


## 1. Application property approach
Set below property in `application.properties` or `application.yml`.

>`debug=true`

## 2. Command-line approach
Or, if we don’t want to use the properties file approach, we can trigger the auto-configuration report by starting the application with the `--debug` switch.


>`java -jar <my_application>.jar --debug`

Both the approaches above print the auto-configuration report on the console during startup. The third is an actuator-based approach that provides the auto-configuration report whenever we need it for diagnostic purposes.

## 3. Actuator approach
Another way to debug auto-configuration is to add a Spring Boot actuator to our project. Add below the dependency in POM.

```
<dependency>	
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
```
Add the property below into `application.properties`
```
management.endpoints.web.exposure.include=*
```
The `/actuator/conditions` endpoint will show the details of all the beans that are auto-configured, and those that are not.

_Don't worry too much about the actuator yet. We have separate bonus lessons to cover it._




In order to debug any production issue, we should know what auto-configurations are applied to the application. Learn how to debug the Spring Boot auto-configuration.

Introduction

Getting Started With Spring Boot

Auto-Configuration In Depth

Database Integration

Expose Rest Webservice

Consuming Rest Webservice

Bonus

Final Words

Debugging Auto-Configuration

Auto-configuration report

1. Application property approach

2. Command-line approach