Quickstart

The quickstart documentation will demonstrate how to install and use the Sakura Boot basic module to create a simple API application.

Prerequisites

See Requirements for prerequisites.

Project structure

Multiple structures are possible when working with Sakura Boot.
For this quickstart API project, the structure is as follows:

📂 project (1)
  📂 src (2)
    📂 main
        📂 java (3)
            📂 com.example.demo (4)
                📂 business (5)
                    📄 SimpleService.java
                📂 persistence (6)
                    📄 SimpleEntity.java
                    📄 SimpleRepository.java
                📂 presentation (7)
                    📄 SimpleController.java
                📄 DemoApplication.java (8)
        📂 resources (9)
            📄 application.properties
            📄 application.yml
  📄 build.gradle.kts (10)
  📄 settings.gradle.kts (11)
  📄 pom.xml (12)
  📄 docker-compose.yml (13)

1	The root directory of the project.
2	Contains the source code of the project.
3	Contains the java code.
4	The java code must be in the package com.example.demo (replace to the actual package name).
5	The business layer of the application (here the services).
6	The persistence layer of the application (here the entities and repositories).
7	The presentation layer of the application (here the controllers).
8	The application entry point.
9	Contains the resources configuration files.
10	The build file (for Gradle).
11	The settings file (for Gradle).
12	The pom file (for Maven).
13	The docker compose file (optional).

To initialize a Spring Boot application, go to https://start.spring.io/. From there, it will be easier to create a new project.

Installation

To install with predefined dependencies for a production-ready application, add one starter to the project dependencies:

With Maven:

This includes the basic functionalities of sakura boot, the necessary spring boot starter, and a runtime postgresql.

<dependency>
    <groupId>org.sansenshimizu.sakuraboot</groupId>
    <artifactId>sakura-boot-starter-predefined-basic</artifactId>
    <version>0.1.1</version>
</dependency>

This includes all the modules of sakura boot, the necessary spring boot starter, mapstruct, ehcache3 as cache provider, and a runtime postgresql.

<dependency>
    <groupId>org.sansenshimizu.sakuraboot</groupId>
    <artifactId>sakura-boot-starter-predefined-all-module</artifactId>
    <version>0.1.1</version>
</dependency>

With Gradle:

This includes the basic functionalities of sakura boot, the necessary spring boot starter, and a runtime postgresql.

implementation("org.sansenshimizu.sakuraboot:sakura-boot-starter-predefined-basic:0.1.1")

This includes all the modules of sakura boot, the necessary spring boot starter, mapstruct, ehcache3 as cache provider, and a runtime postgresql.

implementation("org.sansenshimizu.sakuraboot:sakura-boot-starter-predefined-all-module:0.1.1")

Maven is recommended for developers who never use both Maven and Gradle.

Here is a simple pom.xml file that includes the predefined basic module starter with lombok, spring boot devtools, and spring boot docker compose:

pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>3.3.1</version>
    <relativePath/>
  </parent>
  <groupId>com.example</groupId>
  <artifactId>demo</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <name>demo</name>
  <description>Demo project for Sakura Boot</description>
  <properties>
    <java.version>21</java.version>
  </properties>
  <dependencies>
    <dependency>
        <groupId>org.sansenshimizu.sakuraboot</groupId>
        <artifactId>sakura-boot-starter-predefined-basic</artifactId>
        <version>0.1.1</version>
    </dependency>

    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-devtools</artifactId>
      <scope>runtime</scope>
      <optional>true</optional>
    </dependency>
    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-docker-compose</artifactId>
      <scope>runtime</scope>
      <optional>true</optional>
    </dependency>
    <dependency>
      <groupId>org.projectlombok</groupId>
      <artifactId>lombok</artifactId>
      <optional>true</optional>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-maven-plugin</artifactId>
        <configuration>
          <excludes>
            <exclude>
              <groupId>org.projectlombok</groupId>
              <artifactId>lombok</artifactId>
            </exclude>
          </excludes>
        </configuration>
      </plugin>
      <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.10.0</version>
            <configuration>
                <source>21</source>
                <target>21</target>
                <annotationProcessorPaths>
                    <path>
                        <groupId>org.projectlombok</groupId>
                        <artifactId>lombok</artifactId>
                    </path>
                </annotationProcessorPaths>
            </configuration>
        </plugin>
    </plugins>
  </build>
</project>

Here is an equivalent simple build.gradle.kts.

build.gradle.kts

plugins {
  java
  id("org.springframework.boot") version "3.3.1"
  id("io.spring.dependency-management") version "1.1.6"
}

group = "com.example"
version = "0.0.1-SNAPSHOT"

java {
  toolchain {
    languageVersion = JavaLanguageVersion.of(21)
  }
}

configurations {
  compileOnly {
    extendsFrom(configurations.annotationProcessor.get())
  }
}

repositories {
  mavenCentral()
}

dependencies {
  implementation("org.sansenshimizu.sakuraboot:sakura-boot-starter-predefined-basic:0.1.1")
  compileOnly("org.projectlombok:lombok")
  developmentOnly("org.springframework.boot:spring-boot-devtools")
  developmentOnly("org.springframework.boot:spring-boot-docker-compose")
  annotationProcessor("org.projectlombok:lombok")
}

Configuration

The configuration of the project, like any Spring Boot application, is done in the application.properties (or application.yml) file.

The Spring Boot properties can be configured in this file with the new Sakura Boot properties.

Here is an example of an application.properties file.

application.properties

# SPRING
spring.application.name = demo
spring.threads.virtual.enabled = true
# activate virtual threads

# Controller
server.servlet.context-path = /api

# Cache
spring.jpa.properties.hibernate.cache.use_second_level_cache = true

# Database
spring.jpa.open-in-view = false
spring.datasource.url = jdbc:postgresql://postgres:5432/database
spring.datasource.username = sa
spring.datasource.password = password

# LOG
logging.file.path = ./log/
logging.file.name = ${logging.file.path}${spring.application.name}.log

# Debug
spring.jpa.hibernate.ddl-auto = create-drop
#spring.jpa.show-sql = true
#sakuraboot.exception.showStackTrace = true
#logging.level.com.example.demo = DEBUG
#logging.level.org.sansenshimizu.sakuraboot = DEBUG
#logging.level.root = warn

Those properties are all optional or with a default value.
But it can be a good start for any application.
The Sakura Boot properties work with their related modules. If the module is not used by the application, it can be removed.

For a production-ready application, remove the spring.jpa.hibernate.ddl-auto property.

Create the application

The next part is to write the application code.
The application will use UUID as the primary key of the entity. It is possible to use any other primary key (e.g., Long, String, etc).

Application class

First, the DemoApplication.java will be the same as any Spring Boot application.

DemoApplication.java

@SpringBootApplication
public class DemoApplication {

    public static void main(final String[] args) {

        SpringApplication.run(DemoApplication.class, args);
    }
}

Entity

Then, the entity in SimpleEntity.java will contain all the information that needs to be stored in the database.

An entity is equivalent to one table in the database.

SimpleEntity.java

package com.example.demo.persistence;

import java.io.Serial;
import java.util.List;
import java.util.UUID;

import jakarta.persistence.Column;
import jakarta.persistence.Entity;
import jakarta.persistence.GeneratedValue;
import jakarta.persistence.GenerationType;
import jakarta.persistence.Id;

import org.apache.commons.lang3.tuple.Pair;
import org.hibernate.annotations.Cache;
import org.hibernate.annotations.CacheConcurrencyStrategy;

import org.sansenshimizu.sakuraboot.basic.persistence.AbstractBasicEntity;

@Entity
@Cache(usage = CacheConcurrencyStrategy.READ_WRITE)
public class SimpleEntity extends AbstractBasicEntity<UUID> {

    @Serial
    private static final long serialVersionUID = 412728107151504660L;

    @Id
    @GeneratedValue(strategy = GenerationType.UUID)
    @Column(nullable = false)
    private UUID id;

    private String name;

    // No arg constructor, getters, etc. if lombok is not used.
}

For lombok users, add the annotation on top of the class:

@Getter
@NoArgsConstructor(access = AccessLevel.PACKAGE)
@AllArgsConstructor(access = AccessLevel.PRIVATE)
@Builder(toBuilder = true)
@Entity
@Cache(usage = CacheConcurrencyStrategy.READ_WRITE)

Lombok can help reduce the boilerplate code but needs to be used carefully. see Lombok

Repository

The repository in SimpleRepository.java will be very similar to a Spring Boot repository.

SimpleRepository.java

package com.example.demo.persistence;

import java.util.UUID;

import org.sansenshimizu.sakuraboot.specification.api.persistence.CriteriaRepository;

public interface SimpleRepository extends BasicRepository<SimpleEntity, UUID> {}

Service

The service in SimpleService.java can change based on the modules that are used.

Here is an example of the service that doesn’t use modules.

SimpleService.java

package com.example.demo.business;

import java.util.UUID;

import com.fasterxml.jackson.databind.ObjectMapper;
import org.springframework.stereotype.Service;

import org.sansenshimizu.sakuraboot.basic.api.business.BasicService;

import com.example.demo.persistence.SimpleEntity;
import com.example.demo.persistence.SimpleRepository;
import com.example.demo.presentation.SimpleFilter;

@Service
public class SimpleService implements BasicService<SimpleEntity, UUID> {

    private final SimpleRepository repository;

    private final ObjectMapper objectMapper;

    @Override
    public Class<Simple> getEntityClass() {

        return Simple.class;
    }

    // Required arg constructor, getters, etc. if lombok is not used.
}

For lombok users, add the annotation on top of the class:

@Getter
@RequiredArgsConstructor
@Service

Controller

The controller in SimpleController.java can change based on the modules that are used.

Here is an example of the controller that doesn’t use modules.

SimpleController.java

package com.example.demo.presentation;

import java.util.UUID;

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

import org.sansenshimizu.sakuraboot.basic.api.presentation.BasicController;

import com.example.demo.business.SimpleService;
import com.example.demo.persistence.SimpleEntity;

@RestController
@RequestMapping("/simples")
public class SimpleController
    implements BasicController<SimpleEntity, UUID, SimpleEntity> {

    private final SimpleService service;

    // Required arg constructor, getters, etc. if lombok is not used.
}

For lombok users, add the annotation on top of the class:

@Getter
@RequiredArgsConstructor
@RestController
@RequestMapping("/simples")

The simple application with the basic module is now ready to be used.

Usage

Execute the application

To run the application, execute the following command on a terminal in a root directory of the project:

For Gradle:

./gradlew bootRun

For Maven:

./mvnw spring-boot:run

Use the application

After running the application, it will be available at localhost.
Because the property server.servlet.context-path is set to /api, the application will be available at http://localhost:8080/api.

For this application the simple entity is available at http://localhost:8080/api/simples.

The application will support the common http methods (POST, GET, PUT, PATCH, DELETE).
Example of usage:

Table 1. application usage
Method	Url	Body
POST	http://localhost:8080/api/simples	{"name": "demo"}
GET	http://localhost:8080/api/simples
GET by id	http://localhost:8080/api/simples/id
PUT by id	http://localhost:8080/api/simples/id	{"id": id, "name": "demo"}
PATCH by id	http://localhost:8080/api/simples/id	{"id": id, "name": "demo"}
DELETE by id	http://localhost:8080/api/simples/id

Docker

If the application uses spring-boot-docker-compose, the file docker-compose.yml is necessary in the root directory of the project. It needs to contain at least the database container.

Here is an example of the docker compose file:

docker-compose.yml

services:
  database:
    image: 'postgres:alpine'
    container_name: demo-postgres
    ports:
      - '5432'
    environment:
      - 'POSTGRES_USER=sa'
      - 'POSTGRES_DB=database'
      - 'POSTGRES_PASSWORD=password'

This file is only used to run the application locally.

To build the docker image, execute the following command on a terminal in a root directory of the project:

For Gradle:

./gradlew bootBuildImage

For Maven:

./mvnw spring-boot:build-image

Next steps

For more information on how to build and run a Spring Boot application, see here.

For more information about the spring-boot-docker-compose for local development with docker support, see here.

The quickstart application creates only one entity. The next step could be to add more entities with the necessary fields. For each new entity follow the same steps.

When building an application with different entities, it is possible to create relations between them.
For more information, see the Relationship section.

When building an application, it is important to also create tests.
Sakura Boot provides a test framework that can be used to test the application. It supports unit tests, integration tests, and functional tests.
For more information, see the Testing section.

To customize the configuration for the application requirements, see the Configuration section.

If the quickstart section is not sufficient, other examples are available at the Examples section.