add-entity

To add a JPA entity and repository in Spring Boot 4, you need to generate the entity class, repository interface, and required wiring. This approach also creates a Flyway migration and Testcontainers integration tests to verify repository constraints and behavior.

Choosing between JPA and Spring Data JDBC depends on your domain model structure. JPA suits Hibernate-based object-relational mapping, while Spring Data JDBC is better for aggregate-root-oriented persistence, and both can be configured with Flyway migrations and Testcontainers tests.

Configuring Flyway migrations for a new database table involves creating the required SQL migration script and setting up the datasource so production never relies on Hibernate ddl-auto, ensuring safe schema management alongside your Spring Boot entities.

Testing Spring Data JDBC or JPA repositories with Testcontainers involves running component tests against a real database instance to verify repository correctness and database constraints, ensuring your persistence layer behaves as expected across unit and component layers.

No, this approach is not intended for scaffolding new projects or generating endpoints. It assumes you already have an existing Spring Boot 4 codebase that passes ./gradlew check and only needs a new persistence layer added to store domain models.

Mapping JPA entities to DTOs in a Spring Boot service layer involves creating mapping logic within the service to translate persisted domain objects, ensuring separation between the persistence model and external data contracts while maintaining aggregate root integrity.