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 food delivery company needs a Spring Boot microservice to handle order processing. Build it using Spring Boot 3 and Java 17+.
Domain concepts:
Endpoints:
GET /api/menu -- list all available menu itemsGET /api/menu/:id -- get a single menu itemPOST /api/orders -- place a new order (customerEmail required, at least one item, all items must reference existing available menu items, calculate total automatically)GET /api/orders/:id -- get order details including itemsPATCH /api/orders/:id/status -- update order status (only valid transitions: PENDING->CONFIRMED->PREPARING->DELIVERED, or any->CANCELLED)Business rules:
Use PostgreSQL as the database (provide the schema, the app does not need to actually connect).
Produce a complete Spring Boot project with:
pom.xml with dependencies listedYou may create additional files as needed for a well-structured codebase.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers