Spring Boot REST API for inventory management — products and orders backed by an H2 in-memory database. Part of the GitOps Demo multi-service application.

Browser → Node.js Frontend → Go Catalog Service
                           → Java Inventory Service (this)

The Node.js frontend calls this service for:

• GET /api/v1/products — inventory table on the dashboard
• GET /api/v1/orders — orders table on the dashboard
• POST /api/v1/orders — "Place Demo Order" button

• Java 17, Spring Boot 3.2
• Spring Data JPA + H2 (in-memory, seeded on startup)
• Spring Boot Actuator (health, metrics, info)
• Bean Validation (Jakarta)

curl -X POST http://localhost:8080/api/v1/orders \
  -H 'Content-Type: application/json' \
  -d '{
    "customerName": "Alice Johnson",
    "customerEmail": "alice@demo.com",
    "items": [{"productId": 1, "quantity": 2}]
  }'

8 products are inserted on startup via src/main/resources/data.sql: Electronics (Laptop, Mouse, Keyboard, Monitor, USB Hub), Furniture (Chair, Desk), Stationery (Notebooks).

Prerequisites: Java 17+, Maven 3.8+

mvn spring-boot:run
# Service starts on :8080

curl http://localhost:8080/actuator/health
curl http://localhost:8080/api/v1/products

H2 console available at http://localhost:8080/h2-console (JDBC URL: jdbc:h2:mem:gitopsdb)

# Run tests
mvn test

# Build jar (required before Docker build)
mvn package -DskipTests

# Must build jar first
mvn package -DskipTests

docker build -t demo-java .
docker run -p 8080:8080 demo-java

The Dockerfile copies target/gitops-app-1.0.0.jar — mvn package must run before the Docker build. The gitops-platform compile task handles this automatically.

Manifests are in kubernetes/:

Apply:

kubectl apply -k kubernetes/

Image: Update DOCKERHUB_USER/demo-java:latest in deployment.yaml with your registry image after the CI pipeline builds and pushes it.

When onboarding in the gitops-platform, set:

• Language: Java
• Dockerfile: Dockerfile
• Build context: .
• Compile command: mvn package -DskipTests
• Test command: mvn test