Java Maven Postgres — Blueprint

REST API backend built with Java 21, Spring Boot 3.4.1, and PostgreSQL. Intended as a starting point for Kubernetes-deployed services: one table, one API endpoint, full Docker support out of the box.

Tech stack:

The application starts on port 8080. Opening / in a browser redirects to the Swagger UI at /swagger-ui/index.html.

Project Structure

src/main/java/com/vibeham/template/
├── TemplateApplication.java          # Spring Boot entry point
├── config/
│   └── DataSourceConfig.java         # Custom DataSource bean
├── controller/
│   ├── HomeController.java           # GET / → redirect to Swagger UI
│   ├── InfoController.java           # GET /api/info
│   └── SpaceTargetController.java    # GET /api/targets
├── model/
│   └── SpaceTarget.java              # JPA entity: id, name, type, distanceLightYears
└── repository/
    └── SpaceTargetRepository.java    # Spring Data JPA repository

src/main/resources/
├── application.yml                   # Spring / JPA / Flyway / Swagger config
└── db/migration/
    └── V1__init.sql                  # Creates space_target table + seed data

Key design decisions:

• DataSourceConfig manually constructs the HikariCP DataSource so the app accepts both a single DATABASE_URL (the format issued by most managed cloud databases) and individual DB_* variables. Spring's auto-configuration for DataSource is intentionally bypassed.
• ddl-auto: validate — Hibernate only validates that the schema matches the entities. All schema changes go through Flyway migrations in db/migration/.
• SpaceTarget is the demo entity. To add your own domain: create a new entity in model/, a repository in repository/, a Flyway migration in db/migration/, and a controller in controller/. The demo files can be deleted once you no longer need them.
• The Dockerfile uses a multi-stage build: the first stage (maven:3.9-eclipse-temurin-21) compiles and packages; the second stage (eclipse-temurin:21-jre-alpine) copies only the fat JAR, keeping the final image small.

Environment Variables

The application runs on port 8080 and requires a PostgreSQL database.

Database connection is configured via one of two approaches:

Option A — Single connection URL (recommended for managed services)

The URL must use the postgres:// or postgresql:// scheme. The sslmode query parameter is optional.

Option B — Individual variables

DATABASE_URL takes precedence. If it is set, the individual DB_* variables are ignored.

Running Locally

With Docker Compose

docker compose up

Starts the application together with a PostgreSQL instance and sets DATABASE_URL automatically. No additional configuration needed.

Standalone

# build
mvn package -DskipTests

# run — Option A
DATABASE_URL=postgres://postgres:postgres@localhost:5432/spacedb java -jar target/*.jar

# run — Option B
DB_HOST=localhost DB_USER=postgres DB_PASSWORD=secret java -jar target/*.jar