Creating a Simple CRUD API with Spring Boot and In-Memory Database

Below is a step-by-step guide to create a simple CRUD API using Spring Boot and an in-memory database like H2. We will use Maven to manage the project’s dependencies.

1. Set Up Your Maven Project

Create a new Maven project or directory for the Spring Boot application.

pom.xml

Here is the file with the necessary dependencies: pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>crud-api</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>jar</packaging>
    <name>Spring Boot CRUD API</name>
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>3.5.3</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>

    <properties>
        <java.version>21</java.version>
    </properties>

    <dependencies>
        <!-- Spring Boot Starter Web -->
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>

        <!-- Spring Boot Starter JPA -->
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-data-jpa</artifactId>
        </dependency>

        <!-- H2 Database (In-memory database) -->
        <dependency>
            <groupId>com.h2database</groupId>
            <artifactId>h2</artifactId>
            <scope>runtime</scope>
        </dependency>

        <!-- Lombok for simplicity -->
        <dependency>
            <groupId>org.projectlombok</groupId>
            <artifactId>lombok</artifactId>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <!-- Maven Spring Boot plugin -->
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>
</project>

2. Create the Application Entry Point

src/main/java/org/kodejava/crudapi/CrudApiApplication.java

Create the main class for your Spring Boot application.

package org.kodejava.crudapi;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class CrudApiApplication {

    public static void main(String[] args) {
        SpringApplication.run(CrudApiApplication.class, args);
    }
}

3. Define the Entity

Create a User entity to model your data.

src/main/java/org/kodejava/crudapi/model/User.java

package org.kodejava.crudapi.model;

import jakarta.persistence.*;

import lombok.Data;
import lombok.NoArgsConstructor;

@Data
@NoArgsConstructor
@Entity
@Table(name = "users")
public class User {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String name;

    private String email;
}

4. Create the Repository

The repository will handle database operations.

src/main/java/org/kodejava/crudapi/repository/UserRepository.java

package org.kodejava.crudapi.repository;

import com.example.crudapi.model.User;
import org.springframework.data.jpa.repository.JpaRepository;

public interface UserRepository extends JpaRepository<User, Long> {
}

5. Define the Service

The service layer will handle business logic.

src/main/java/org/kodejava/crudapi/service/UserService.java

package org.kodejava.crudapi.service;

import com.example.crudapi.model.User;
import com.example.crudapi.repository.UserRepository;
import org.springframework.stereotype.Service;

import java.util.List;

@Service
public class UserService {

    private final UserRepository userRepository;

    public UserService(UserRepository userRepository) {
        this.userRepository = userRepository;
    }

    public List<User> getAllUsers() {
        return userRepository.findAll();
    }

    public User getUserById(Long id) {
        return userRepository.findById(id).orElseThrow(() -> new RuntimeException("User not found"));
    }

    public User createUser(User user) {
        return userRepository.save(user);
    }

    public User updateUser(Long id, User user) {
        User existingUser = getUserById(id);
        existingUser.setName(user.getName());
        existingUser.setEmail(user.getEmail());
        return userRepository.save(existingUser);
    }

    public void deleteUser(Long id) {
        userRepository.deleteById(id);
    }
}

6. Create the Controller

The controller defines API endpoints for CRUD operations.

src/main/java/org/kodejava/crudapi/controller/UserController.java

package org.kodejava.crudapi.controller;

import com.example.crudapi.model.User;
import com.example.crudapi.service.UserService;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.*;

import java.util.List;

@RestController
@RequestMapping("/api/users")
public class UserController {

    private final UserService userService;

    public UserController(UserService userService) {
        this.userService = userService;
    }

    @GetMapping
    public ResponseEntity<List<User>> getAllUsers() {
        return ResponseEntity.ok(userService.getAllUsers());
    }

    @GetMapping("/{id}")
    public ResponseEntity<User> getUserById(@PathVariable Long id) {
        return ResponseEntity.ok(userService.getUserById(id));
    }

    @PostMapping
    public ResponseEntity<User> createUser(@RequestBody User user) {
        return ResponseEntity.status(HttpStatus.CREATED).body(userService.createUser(user));
    }

    @PutMapping("/{id}")
    public ResponseEntity<User> updateUser(@PathVariable Long id, @RequestBody User user) {
        return ResponseEntity.ok(userService.updateUser(id, user));
    }

    @DeleteMapping("/{id}")
    public ResponseEntity<Void> deleteUser(@PathVariable Long id) {
        userService.deleteUser(id);
        return ResponseEntity.noContent().build();
    }
}

7. Configure Application Properties

Configure the H2 database in . application.properties

src/main/resources/application.properties

# H2 In-Memory Database Settings
spring.datasource.url=jdbc:h2:mem:testdb
spring.datasource.driverClassName=org.h2.Driver
spring.datasource.username=sa
spring.datasource.password=password
spring.jpa.database-platform=org.hibernate.dialect.H2Dialect
spring.h2.console.enabled=true
spring.h2.console.path=/h2-console

8. Test the Application

Run your Spring Boot application and test the REST APIs using tools like Postman or curl.

  • To get all users:
  GET http://localhost:8080/api/users
  • To get a user by ID:
  GET http://localhost:8080/api/users/{id}
  • To create a user:
  POST http://localhost:8080/api/users
  Content-Type: application/json
  {
      "name": "John Doe",
      "email": "[email protected]"
  }
  • To update a user:
  PUT http://localhost:8080/api/users/{id}
  Content-Type: application/json
  {
      "name": "Jane Doe",
      "email": "[email protected]"
  }
  • To delete a user:
  DELETE http://localhost:8080/api/users/{id}

9. Access the H2 Console

You can access the H2 database console at http://localhost:8080/h2-console.

  • JDBC URL: jdbc:h2:mem:testdb
  • Username: sa
  • Password: password

That’s it! You now have a fully functional CRUD API with Spring Boot and an in-memory H2 database.

Spring Boot Configuration Essentials: application.properties vs application.yml

In Spring Boot, both application.properties and application.yml are configuration files used to define application settings, but they differ mainly in syntax and structure. Here’s a detailed comparison to help you understand their essentials:

1. File Format

application.properties:

  • A key-value pair format, where each property is defined on a new line.
  • A simple and widely used format for configuration files.

Example:

server.port=8080
spring.datasource.url=jdbc:mysql://localhost:3306/mydb
spring.datasource.username=admin
spring.datasource.password=secret

application.yml:

  • A hierarchical data format popular for its readability, using indentation to denote levels.
  • Based on YAML syntax, it is more concise for complex hierarchical configurations.

Example:

server:
  port: 8080

spring:
  datasource:
    url: jdbc:mysql://localhost:3306/mydb
    username: admin
    password: secret

2. Structure and Readability

  • application.properties: Flat structure; can get lengthy and harder to read with nested configurations.
  • application.yml: More concise and easier to maintain hierarchical data (e.g., grouping related properties).

For instance:

  • Nested configuration in application.properties:
  spring.datasource.url=jdbc:mysql://localhost:3306/mydb
  spring.datasource.username=admin
  spring.datasource.password=secret
  spring.jpa.hibernate.ddl-auto=update
  • Nested configuration in application.yml:
  spring:
    datasource:
      url: jdbc:mysql://localhost:3306/mydb
      username: admin
      password: secret
    jpa:
      hibernate:
        ddl-auto: update

3. Multi-Profile Support

  • Both formats support profiles (e.g., application-dev.properties or application-dev.yml).
  • However, in application.yml, profiles are defined more elegantly using spring.profiles.

Example in application.properties:

# application-dev.properties
spring.datasource.url=jdbc:mysql://localhost:3306/devdb

Example in application.yml:

spring:
  profiles:
    active: dev

---
spring:
  profiles: dev
  datasource:
    url: jdbc:mysql://localhost:3306/devdb

The --- in YAML separates different profiles, while spring.profiles specifies the active one.

4. Comments

  • application.properties: Use # for single-line comments.
    Example:
  # This sets the server's port
  server.port=8080
  • application.yml: Also uses # for comments.
    Example:
  # This sets the server's port
  server:
    port: 8080

5. Tools and Validation

  • YAML syntax errors (like incorrect indentation) are harder to debug compared to properties.
  • Most IDEs (like IntelliJ IDEA) provide excellent support for both formats, with syntax highlighting and validation tools.

6. When to Use Which?

  • Use application.properties:
    • If you prefer simplicity and are comfortable with key-value pairs.
    • For flat and straightforward configurations.
  • Use application.yml:
    • If you want a more structured and readable format.
    • For more complex hierarchical configurations or when working with deeply nested values.

7. Mixing Both

  • Spring Boot supports both application.properties and application.yml in the same project, but it’s recommended to stick to one for consistency.
  • If both exist, application.properties takes precedence over application.yml (as per Spring Boot’s default property source order).

Summary Table:

Aspect application.properties application.yml
Format Key-value pair Hierarchical YAML format
Readability Harder for nested values Easy to read and maintain with indentation
Profiles Separate files for each profile Inline profiles with --- separator
Error handling Simple; less prone to errors Easy to misconfigure due to indentation
Preference Flat structure Complex or hierarchical configuration

Using Spring Boot DevTools for Faster Development and Live Reload

Spring Boot DevTools is a valuable tool for speeding up the development process by enabling features like automatic application restart and live reload of web content. It is specifically designed to improve the development experience by reducing the time required to restart the application during testing and debugging.

Here is a quick guide to using Spring Boot DevTools for faster development and live reload:


1. Add DevTools Dependency

To use Spring Boot DevTools, include it in your pom.xml (Maven) or build.gradle (Gradle) file.

Using Maven:

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-devtools</artifactId>
    <optional>true</optional>
</dependency>

Using Gradle:

implementation 'org.springframework.boot:spring-boot-devtools'

2. Automatic Restart

Spring Boot DevTools triggers an automatic application restart whenever files in the classpath are modified. It uses two classloaders—one for the static resources and one for the application classes—enabling a fast reload experience.

  • Restart Triggering: Files located under /src/main/resources/, /src/main/java/, or any other classpath resources automatically restart the application upon modification.
  • Excluding Certain Files from Restart: You can exclude specific file patterns using the property:
spring.devtools.restart.exclude=static/**,public/**

3. Live Reload (Optional with Browser)

Spring Boot DevTools integrates with LiveReload, so front-end changes (e.g., HTML, CSS, or JavaScript) trigger an automatic browser reload.

Steps for LiveReload:

  1. Install a LiveReload extension in your browser (available for Chrome, Firefox, etc.).
  2. DevTools will automatically enable LiveReload if the extension is active.

If you want to disable the LiveReload capability, use the following property:

spring.devtools.livereload.enabled=false

4. Property Defaults in Development vs. Production

DevTools provides sensible defaults for development environments that are different from production. For instance:

  • Caching is disabled for templates (e.g., Thymeleaf, FreeMarker, etc.).
  • Hibernate auto-detection for changes in the database schema is enabled.

If you want to customize DevTools properties, you can use a dedicated application-dev.properties profile.

5. How to Enable Conditional DevTools Behavior

To avoid shipping DevTools to production, mark it as optional=true in Maven or use a developmentOnly configuration in Gradle.

Example for Gradle:

developmentOnly 'org.springframework.boot:spring-boot-devtools'

6. Disable Restart in Specific Scenarios

If you don’t want restart functionality during your development, you can disable it with the property:

spring.devtools.restart.enabled=false

7. Trigger a Manual Restart

If you want to trigger a restart manually during development, you can:

  • Add or remove files in the /META-INF/spring-devtools.properties directory to trigger a restart.

8. Example Use Case: Thymeleaf or Front-End Modification

If you’re using Thymeleaf templates in a Spring Boot application for the web frontend:

  • Modify an HTML file under /src/main/resources/templates.
  • The browser will refresh automatically (if LiveReload is enabled). You’ll instantly see your changes without manually restarting or refreshing.

Important Notes:

  • Spring Boot DevTools is solely for development purposes and should not be packaged into your production build.
  • If you’re running in Docker or a cloud environment, ensure that file watchers are properly configured for file changes.

Incorporating Spring Boot DevTools provides a more efficient development experience by automating repetitive actions and making live coding efforts more seamless!

Building Your First REST API with Spring Boot in Under 10 Minutes

Creating a simple REST API using Spring Boot can be a smooth process, and it is entirely possible to get it done in under 10 minutes. Here’s a step-by-step guide to building your first REST API:

1. Setup Your Spring Boot Project

  1. Go to Spring Initializr.
  2. Configure the project:
    • Project: Maven.
    • Language: Java.
    • Spring Boot Version: Choose the latest stable version.
    • Dependencies: Add Spring Web (this adds support for creating a REST API).
  3. Click to download the project as a .zip file. Generate

  4. Extract the file, then open it in your favorite IDE like IntelliJ IDEA.

2. Create a REST Controller

A REST controller handles HTTP requests and maps them to methods. You will use the @RestController annotation to create a REST API in Spring Boot.
Create a file under src/main/java/com/example/demo/ named : HelloWorldController.java

package com.example.demo;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/api")
public class HelloWorldController {

    @GetMapping("/hello")
    public String helloWorld() {
        return "Hello, World!";
    }
}
  • Annotations Explained:
    • @RestController: Combines @Controller and @ResponseBody, enabling REST-specific behavior.
    • @RequestMapping: Specifies the base path for this controller (e.g., /api).
    • @GetMapping: Handles HTTP GET requests for the /hello sub-endpoint.

3. Run Your Application

  1. Run your application by navigating to the DemoApplication class and executing the method (Run button in IntelliJ). main
  2. By default, your application will start on port 8080.

4. Test Your REST API

Hello, World!

5. (Optional) Add Another Endpoint Returning JSON

If you want to return a JSON response, create a new endpoint:

@GetMapping("/greet")
public Greeting greetUser() {
    return new Greeting("Welcome to Spring Boot!");
}

Create a new class Greeting.java under the same package:

package com.example.demo;

public class Greeting {

    private String message;

    public Greeting(String message) {
        this.message = message;
    }

    public String getMessage() {
        return message;
    }

    public void setMessage(String message) {
        this.message = message;
    }
}
{
    "message": "Welcome to Spring Boot!"
}

6. Complete!

Congratulations, you’ve successfully created your first REST API with Spring Boot!

How Dependency Injection Works in Spring Boot Using @Autowired

Dependency Injection (DI) is a fundamental concept in Spring Boot that facilitates the management of dependencies between various components in your application. Spring Boot primarily uses the @Autowired annotation to enable automatic wiring of beans. Below, I’ll explain how Dependency Injection works using @Autowired in Spring Boot, step by step.

What is Dependency Injection?

Instead of creating dependencies manually within components, Spring’s IoC (Inversion of Control) container injects dependencies into an object automatically. This reduces tight coupling and makes code more reusable and flexible.

How Does @Autowired Work?

@Autowired is used to mark a dependency that Spring should handle automatically. It tells Spring, “Find the appropriate bean in the IoC container and inject it here.”

Here’s how it works:

  1. Mark the class as a Spring Bean using @Component, @Service, @Repository, or by defining it explicitly via @Bean in a configuration class.
  2. Use the @Autowired Annotation to inject a required dependency into a field, constructor, or setter method.

Approaches to Using @Autowired

1. Field Injection

This is the simplest form of dependency injection where the field is annotated with @Autowired.

import org.springframework.stereotype.Component;
import org.springframework.beans.factory.annotation.Autowired;

@Component
public class CarService {

    @Autowired
    private Engine engine;

    public void startCar() {
        engine.start();
    }
}
@Component
public class Engine {
    public void start() {
        System.out.println("Engine started!");
    }
}
  • Pros: Quick and readable.
  • Cons: Field injection is less testable and not recommended for complex applications because the dependency is hard to mock in unit tests.

2. Constructor Injection (Recommended)

Here, dependencies are injected via the constructor. This is the most preferred approach as it promotes immutability and easy testing.

import org.springframework.stereotype.Component;

@Component
public class CarService {

    private final Engine engine;

    @Autowired // Optional in Spring Boot since 4.3+
    public CarService(Engine engine) {
        this.engine = engine;
    }

    public void startCar() {
        engine.start();
    }
}
@Component
public class Engine {
    public void start() {
        System.out.println("Engine started!");
    }
}
  • Pros: Cleaner, better for unit testing, adheres to immutability principles.
  • Cons: Requires explicit constructors, but modern tools (e.g., Lombok) simplify this.

3. Setter Injection

Dependencies are injected via setter methods. This is helpful when a bean property is optional and not required during object creation.

import org.springframework.stereotype.Component;
import org.springframework.beans.factory.annotation.Autowired;

@Component
public class CarService {

    private Engine engine;

    @Autowired
    public void setEngine(Engine engine) {
        this.engine = engine;
    }

    public void startCar() {
        engine.start();
    }
}
@Component
public class Engine {
    public void start() {
        System.out.println("Engine started!");
    }
}
  • Pros: Useful when you want to inject optional dependencies.
  • Cons: Makes the class mutable and harder to test.

Behind the Scenes

  1. Bean Discovery: The Spring IoC container detects beans annotated with @Component, @Service, @Repository, @Controller, or those defined explicitly in configuration classes.
  2. Dependency Resolution: When @Autowired is detected on a field, constructor, or setter, Spring scans its ApplicationContext to find a matching bean (by type).
  3. Injection: The resolved bean (dependency) is injected into the target where @Autowired is present.

Handling Ambiguity

If multiple beans of the same type are defined, Spring would throw a NoUniqueBeanDefinitionException. You can resolve this by:

  • Using @Qualifier:
@Autowired
@Qualifier("specificEngine")
private Engine engine;
  • Marking a bean as a primary candidate:
@Primary
@Component
public class Engine { ... }

Example: A Working Spring Boot Application

Here’s a complete example of how @Autowired can be used in a Spring Boot application.

Application Entry Point

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class SpringBootExampleApplication {
    public static void main(String[] args) {
        SpringApplication.run(SpringBootExampleApplication.class, args);
    }
}

Service & Dependency

import org.springframework.stereotype.Service;

@Service
public class GreetingService {

    public String getGreeting() {
        return "Hello, Dependency Injection!";
    }
}
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class GreetingController {

    private final GreetingService greetingService;

    public GreetingController(GreetingService greetingService) {
        this.greetingService = greetingService;
    }

    @GetMapping("/greet")
    public String greet() {
        return greetingService.getGreeting();
    }
}

Run the application, and visiting http://localhost:8080/greet will give you the message:
Hello, Dependency Injection!

Best Practices

  1. Use Constructor Injection for mandatory dependencies.
  2. Avoid Field Injection, except for small applications or testing purposes.
  3. Annotate beans properly using stereotypes like @Service, @Component, etc.
  4. For optional beans, use @Autowired(required = false) or setter injection.
  5. Handle bean ambiguity with @Qualifier or @Primary.

Understanding @SpringBootApplication: The Heart of a Spring Boot App

The @SpringBootApplication annotation is a cornerstone of any Spring Boot application. It simplifies the configuration process and integrates core functionalities of Spring Boot in a single, convenient annotation. Here’s a comprehensive explanation to help you understand its importance and functionality:


What is @SpringBootApplication?

@SpringBootApplication is a composite annotation that combines three common Spring annotations to reduce configuration complexity. These annotations are:

  1. @SpringBootConfiguration
    • Denotes that this class is a configuration class.
    • Equivalent to Spring’s @Configuration annotation.
    • Allows the application to define @Bean definitions and Spring container settings.
  2. @EnableAutoConfiguration
    • Enables Spring Boot’s auto-configuration mechanism.
    • Automatically configures the Spring application based on the dependencies declared in the project.
    • For instance, if spring-boot-starter-web is in your dependencies, it will configure web-related beans like DispatcherServlet, ViewResolvers, etc.
  3. @ComponentScan
    • Scans the package where the annotated class resides and its sub-packages for Spring components (e.g., @Component, @Service, @Repository, @Controller, etc.).
    • This ensures that all required Spring-managed components are registered in the application context.

By combining these three annotations, @SpringBootApplication provides a streamlined way to configure and bootstrap Spring Boot applications.


Advantages of @SpringBootApplication

  1. Reduced Boilerplate Code
    Developers don’t need to explicitly annotate the main application class with @Configuration, @EnableAutoConfiguration, and @ComponentScan. The single annotation @SpringBootApplication takes care of it all.

  2. Auto-Configuration
    The @EnableAutoConfiguration part ensures that Spring Boot configures most components for you based on the classpath dependencies.

  3. Ease of Use
    Simplifies managing configurations and makes the application easier to understand and develop.


Where Should You Place @SpringBootApplication?

The @SpringBootApplication annotation is typically placed on the main class of the application, which is also the entry point for the main method. By convention, this main class should be located in the base package of the application. This ensures that the @ComponentScan directive will pick up all components, services, and controllers in sub-packages.

For example:

package org.kodejava.springboot.demo;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}

If your application’s main class is not located in the base package, you’ll need to manually configure the package path using the @ComponentScan annotation.


Customization Options of @SpringBootApplication

In some scenarios, you might want to override the default behavior of @SpringBootApplication by customizing its inner behavior:

  • Excluding Certain Auto-Configurations
    If you want to disable specific parts of Spring Boot’s auto-configuration:
@SpringBootApplication(exclude = {DataSourceAutoConfiguration.class})
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}
  • Setting Scanning Packages
    You can explicitly define scanning behavior using the @ComponentScan annotation:
@SpringBootApplication
@ComponentScan(basePackages = {"org.kodejava.springboot.demo.service", "org.kodejava.springboot.demo.dao"})
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}

Keynotes

  1. Auto-Configuration Priority:
    • Auto-configuration mechanisms can be fine-tuned or overridden through application.properties or custom configuration classes.
  2. SpringApplication.run:
    • This method in the main method initializes the Spring application context and launches it.
  3. Custom Beans:
    • @SpringBootApplication does not prevent you from defining custom Beans or configurations if needed. You can still use annotations like @Bean and @Configuration alongside it.

Conclusion

@SpringBootApplication eliminates a lot of boilerplate code, making Spring Boot applications easier to configure and start. It combines the functionality of several essential Spring annotations into one. For most Spring Boot applications, simply annotating the main class with @SpringBootApplication is sufficient to bootstrap the application with sensible defaults, making it the “heart” of any Spring Boot app!


Maven Dependencies

<dependencies>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter</artifactId>
        <version>3.4.4</version>
    </dependency>
</dependencies>

Maven Central

How to Create Your First Spring Boot Project Using Spring Initializr

Here’s a step-by-step guide for creating your first Spring Boot project using Spring Initializr:

Step 1: Go to Spring Initializr

  1. Open the Spring Initializr website: https://start.spring.io/.
  2. You will see a friendly interface that allows you to configure your new Spring Boot project.

Step 2: Configure Your Project

  1. Project Settings:
    • Project Type: Choose either Maven or Gradle (Maven is common for beginners).
    • Language: Select Java, Kotlin, or Groovy. Use Java for now to keep it simple.
    • Spring Boot Version: Select the latest stable version (e.g., 3.x.x).
  2. Project Metadata:
    • Group: Enter your domain or namespace (e.g., com.example).
    • Artifact: This is the name of your project (e.g., demo).
    • Name and Description: Optional, but you can customize these values.
    • Package Name: Auto-generated from Group and Artifact but can be edited.
    • Packaging: Choose Jar.
    • Java Version: Select the Java version installed on your machine (e.g., Java 23 for compatibility).
  3. Dependencies:
    • Click Add Dependencies and search for the necessary modules, such as:
      • Spring Web for building web applications (REST APIs, etc.).
      • Spring Data JPA if you want database integration.
      • H2 Database for testing with an in-memory database.
      • Spring Boot DevTools for automatic application reload during development.

Add any additional dependencies you need for your project.

Step 3: Download the Project

  1. After configuring your project, click on the Generate button.
  2. A .zip file containing your project will be downloaded.

Step 4: Import the Project into IntelliJ IDEA

  1. Open IntelliJ IDEA.
  2. Go to File > Open and select the folder where you extracted your project.
  3. If IntelliJ suggests importing the project as a Maven/Gradle project, confirm the selection.
  4. Upon importing the project, IntelliJ will automatically resolve and download the dependencies.

Step 5: Run the Spring Boot Application

  1. Locate the main class in the project. It is usually located in src/main/java/<package-name> and has an @SpringBootApplication annotation.
  2. Right-click on the main class and select Run .
  3. Once the application starts, you will see the Spring Boot banner in the console and a log message indicating that the application started successfully.

Example Project Structure

Here’s a high-level view of what your project structure will look like:

src
├── main
|   ├── java
|   │   └── com.example.demo
|   │       └── DemoApplication.java (Main class)
|   └── resources
|       ├── application.properties (Configuration file)
|       ├── static
|       └── templates
└── test

Next Steps

  • Open the application.properties file in the src/main/resources/ directory to specify configuration data, such as database properties.
  • Start building your business logic, controller classes, and database entities.

Congratulations! 🎉 You’ve successfully created your first Spring Boot project using Spring Initializr.

Spring Boot vs. Spring Framework: What’s the Difference?

Spring Boot and Spring Framework are closely related but serve distinct purposes in the world of Java development. Below is a comparison that highlights the key differences between the two:

1. Core Definition

  • Spring Framework:
    • A comprehensive framework that provides tools, libraries, and features to build a wide variety of Java applications. It includes modules such as Spring Core, Spring MVC, Spring Security, and more.
  • Spring Boot:
    • A framework built on top of the Spring Framework to simplify the development of Spring-based applications. It helps developers create standalone, production-ready applications with minimal configuration.

2. Configuration

  • Spring Framework:
    • Requires extensive XML configurations or Java-based configurations to set up an application.
    • Developers need to explicitly define and configure many components (e.g., beans, data sources, etc.).
  • Spring Boot:
    • Minimizes configuration by using auto-configuration and conventions over configurations.
    • Relies heavily on annotations like @SpringBootApplication, and dependencies are simplified via starters (e.g., spring-boot-starter-web, spring-boot-starter-data-jpa).
    • Enables a “just works” approach by setting up sensible defaults for most use cases.

3. Startup

  • Spring Framework:
    • Applications often rely on external application servers like Tomcat or Jetty for deployment. Configuration for deployment can be complex.
  • Spring Boot:
    • Provides an embedded application server (Tomcat, Jetty, or Undertow) so you can run the application directly—just like running a standalone Java program (using java -jar).
    • Simplifies startup and testing with its self-contained nature.

4. Dependencies

  • Spring Framework:
    • Developers need to manually manage dependencies for different project components and modules.
  • Spring Boot:
    • Uses Spring Boot starters, which are curated dependency descriptors that include the most commonly used libraries for specific types of applications.

5. Microservices

  • Spring Framework:
    • Not specifically designed for microservices but can be adapted with custom configurations.
  • Spring Boot:
    • Designed with microservices in mind. Provides embedded servers, REST API support, and tools like Spring Cloud to facilitate development and deployment of microservices.

6. Build and Deployment

  • Spring Framework:
    • Requires build tools to configure the application and deploy it on external application servers separately.
  • Spring Boot:
    • Generates standalone executable JAR or WAR files that include everything needed to run the application.

7. Learning Curve

  • Spring Framework:
    • Has a steeper learning curve because developers need to understand its modules and configure them manually.
  • Spring Boot:
    • Easier to get started with, thanks to its auto-configuration, starters, and reduced boilerplate code.

8. Use Cases

  • Spring Framework:
    • Suitable for complex, large-scale enterprise applications where fine-grained control over configurations, and application structures is needed.
  • Spring Boot:
    • Ideal for microservices architecture, cloud-native applications, rapid development, prototyping, and small to medium-sized applications.

9. Ecosystem

  • Both Spring Boot and Spring Framework are part of the broader Spring ecosystem. Spring Boot internally leverages the Spring Framework, so it doesn’t replace it but rather enhances it and makes it easier to use.

Example:

  • Spring Framework:
    Developers must explicitly set up dependencies, configure a dispatcher servlet, configure beans, and set up XML or Java-based configuration.
  • Spring Boot:
    A single annotation (@SpringBootApplication) bootstraps the application with default settings, embedded servers, and pre-configured components.

In Summary:

Think of Spring Boot as an opinionated way to work with the Spring Framework. If you need fine-grained control and customization, you’ll likely lean toward the Spring Framework. If you prefer convenience, rapid development, and minimal configuration, Spring Boot is the better choice.

What Is Spring Boot? A Beginner’s Introduction to Rapid Java Development

Spring Boot is a framework designed to simplify and speed up the development of Java-based applications, especially for web and microservices. It’s built on top of the Spring Framework but offers additional features to reduce the complexity of configuration, making it ideal for developers who want to quickly get started with production-ready applications. Below is an introduction to Spring Boot for beginners:


Key Features of Spring Boot

  1. Auto-Configuration:
    • Spring Boot automatically configures your application based on the libraries and dependencies it detects on the classpath. For example, if you include a library for an in-memory database like H2, Spring Boot configures a data source for you automatically.
  2. Embedded Servers:
    • Spring Boot comes with embedded HTTP servers (like Tomcat, Jetty, or Undertow) so you can run your web applications without deploying them to an external server.
  3. Starter Dependencies:
    • To simplify dependency management, Spring Boot provides “starter” dependencies—a curated set of libraries for specific functionalities. For example, spring-boot-starter-web is used for building web applications.
  4. Production-Ready Features:
    • Out of the box, it includes several production-ready features like health checks, metrics, and application monitoring via the Spring Boot Actuator module.
  5. Convention over Configuration:
    • Spring Boot adheres to the “convention over configuration” philosophy, which minimizes the need for manual setup. It works with sensible defaults but allows for customization where required.
  6. Developer Tools:
    • Spring Boot DevTools enhances the development experience by enabling features like hot reloading, which speeds up development cycles.

Why Use Spring Boot?

  • Rapid Development:
    Its default configurations allow developers to create standalone applications quickly without needing to write boilerplate code.
  • Microservices-Friendly:
    Spring Boot is highly suitable for building microservices architectures, thanks to its lightweight setup and embedded server capabilities.
  • Seamless Integration:
    It integrates easily with other Spring projects (e.g., Spring Data, Spring Security, etc.) and third-party libraries.
  • Great Ecosystem:
    The expansive Spring ecosystem includes numerous supported tools and plugins.
  • Minimized XML Configuration:
    You no longer need to deal with verbose XML configurations that were common in traditional Spring Framework setups, as most configurations can now be done using annotations or property files.

How Spring Boot Works

When creating a Spring Boot application:

  1. Start with a Starter Project:
    Use Spring Initializr, a web-based tool, to generate a base project with the desired dependencies.
  2. Dependency Injection:
    Utilize Spring’s core dependency injection (IoC Container) to wire together application components.
  3. Annotations:
    Spring Boot provides a set of annotations like @SpringBootApplication, @RestController, and @Bean to simplify development.
  4. Application Properties:
    The application.properties (or application.yml) file is used to customize configurations.
  5. Single Entry Point:
    Applications built with Spring Boot typically have a main class annotated with @SpringBootApplication, which acts as an entry point for the application.

Hello World Example with Spring Boot

Here’s an example of a basic Spring Boot application:

// Main application class
package org.kodejava.spring;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}
// Example REST Controller
package org.kodejava.spring;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloWorldController {
    @GetMapping("/")
    public String helloWorld() {
        return "Hello, World!";
    }
}

To run this application:

  1. Run the DemoApplication class.
  2. Open a browser and navigate to `http://localhost:8080` to see “Hello, World!”

When to Use Spring Boot

  • You want to rapidly build standalone web or microservices.
  • You prefer convention over configuration.
  • You need ready-to-use tools for monitoring, metrics, and controlling your applications.
  • You want the simplicity of an embedded web server for quick deployment.

Conclusion

Spring Boot is a powerful framework that makes Java development faster, simpler, and more streamlined. Its rich ecosystem, ease of use, and production-ready features make it a great choice for developers at all levels, from beginners to experienced professionals.


Maven Dependencies

<dependencies>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
        <version>3.4.4</version>
    </dependency>
</dependencies>