Enhancing Data Integrity in Ryuu-no-Mi Master-Spring-Boot-3-web-apps

The Problem

When building robust web applications, relying solely on basic database constraints is often insufficient to catch data quality issues early. In our Ryuu-no-Mi project, we noticed that raw input data reaching our service layer lacked sufficient validation, leading to potential persistence errors and inconsistent entity states before they even reached the Hibernate layer.

The Approach

We implemented a two-tiered validation strategy for our Product entities to ensure that only clean, well-formed data enters the system.

Layer 1: Standard Constraints

We utilized standard Bean Validation (JSR 380) annotations to enforce fundamental rules directly on the entity properties. This prevents null or invalid data from triggering unnecessary database roundtrips.

public class Product {
    @NotBlank(message = "Product name cannot be empty")
    @Size(min = 3, max = 100)
    private String name;

    @Positive(message = "Price must be greater than zero")
    private BigDecimal price;
}

Layer 2: Custom Validation Logic

For complex business rules, such as verifying specific stock codes or cross-field validation, we created custom validators. This keeps our service layer clean by offloading validation responsibility to the entity lifecycle.

@Target({ElementType.FIELD})
@Retention(RetentionPolicy.RUNTIME)
@Constraint(validatedBy = ProductCodeValidator.class)
public @interface ValidProductCode {
    String message() default "Invalid product SKU format";
    Class<?>[] groups() default {};
    Class<? extends Payload>[] payload() default {};
}

By integrating these directly with Spring Boot's validation framework, we caught malformed inputs during the initial request binding process, saving processing power and improving API feedback quality.

Key Insight

Moving validation as close to the data model as possible creates a "fail-fast" architecture. By combining default Hibernate/JPA annotations with custom validator interfaces, you reduce the surface area for bugs in your business logic layer.

Takeaway

Start by auditing your most critical entities for missing @NotNull or @Size constraints, then graduate to custom annotations for any domain-specific logic that currently exists inside your service methods.

Generated with Gitvlg.com