Spring Boot project structure — package-by-feature, record DTOs, Flyway migrations, multi-profile config, actuator, proper test structure
84
76%
Does it follow best practices?
Impact
97%
4.04xAverage score across 5 eval scenarios
Passed
No known issues
A warehouse company needs a Spring Boot service to track product inventory across multiple warehouse locations. Build it with Spring Boot 3 and Java 17+.
Domain concepts:
Endpoints:
POST /api/products -- create a product (sku must be unique, name required)GET /api/products -- list products, optional filter by categoryGET /api/products/:id -- get product detailsPOST /api/warehouses -- register a warehouseGET /api/warehouses -- list all warehousesPOST /api/inventory/receive -- receive stock (productId, warehouseId, quantity to add)POST /api/inventory/transfer -- transfer stock between warehouses (productId, fromWarehouseId, toWarehouseId, quantity)GET /api/inventory/product/:productId -- get stock levels across all warehouses for a productBusiness rules:
Use PostgreSQL for the database.
Produce a complete Spring Boot project with:
pom.xml with dependenciesYou may create additional files as needed.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers