Overview & Architecture Pattern
Production relational persistence featuring Spring Data JPA, PostgreSQL, Liquibase/Flyway migrations, and HikariCP.
Architecture Pattern: Data & Persistence
Primary Use Case: Production relational backends requiring automated schema migrations and ACID transactions.
Included Dependencies & Starters
spring-boot-starter-web, data-jpa, postgresql, flyway / liquibase, validation
Domain Entities & Scaffolding Defaults
Customer (UUID, firstName, lastName, email, phone), Address (street, city, state, zipCode, country)
Quickstart: Running Your Project
# 1. Start required infrastructure containers
docker compose up -d
# 2. Run the Spring Boot 3.4 application (Maven)
./mvnw spring-boot:run
# Or run with Gradle
./gradlew bootRun
Frequently Asked Questions
- What starters are included in the CRUD with PostgreSQL & JPA blueprint?
- The CRUD with PostgreSQL & JPA blueprint includes spring-boot-starter-web, data-jpa, postgresql, flyway / liquibase, validation, pre-configured application.yml properties, and production-ready connection pools.
- How do I run the generated CRUD with PostgreSQL & JPA project locally?
- Extract the downloaded ZIP, start dependencies with 'docker compose up -d', and execute './mvnw spring-boot:run' (Maven) or './gradlew bootRun' (Gradle).
- Can I customize entities and database schemas in this blueprint?
- Yes, SpringForge allows you to visually add or modify JPA entities, field types, validation rules, and relational mappings, or import SQL DDL schemas.