How denmette/pizza-kata works
Project type and purpose
• This is a monolithic REST-style backend service built with Spring Boot that exposes a single /order endpoint to place pizza orders.
• Its primary responsibilities are: accept incoming JSON requests, apply domain logic (estimate time, handle toppings), persist orders, and return a response.
File structure
• Top‐level files:
• pom.xml + mvnw/mvnw.cmd → Maven build & dependency management
• compose.yaml → Docker Compose configuration (for PostgreSQL container)
• README.md → project description and usage guidelines
• src/main/java/.../pizza/kata
• PizzaKataApplication.java → Spring Boot entry point
• OrderController.java → REST API layer
• PizzaOrder.java → domain model (JPA entity)
• PizzaOrderRepository.java → persistence layer (Spring Data JPA)
• src/main/resources
• application.properties → config for H2 or external PostgreSQL
• schema.sql/data.sql → database schema & seed data
• src/test → unit + integration tests, including Testcontainers setup
Extract insights from the README
• The application currently uses in-memory H2, but the goal is to switch to PostgreSQL via Docker Compose or Testcontainers
• Phases of work: refactor into cleaner layers (SOLID), add toppings feature, replace database approach
a. Client (e.g. curl, Postman)
b. REST API layer (OrderController)
c. Domain layer / business logic (services or methods inside domain objects)
d. Persistence layer (PizzaOrderRepository)
e. Database
• H2 (in-memory) for local quick run
• PostgreSQL container (via compose.yaml) or ephemeral Testcontainers instance during CI/tests
f. Build & deploy artifacts (Maven, Docker Compose)
Relationships & data flow
• Client → HTTP POST /order → OrderController
• Controller → (injects) Domain/Service → calculates estimatedTime, applies toppings
• Service → PizzaOrderRepository → writes/reads from DB
• Database container (PostgreSQL) ↔ network of the application (managed by Docker Compose or Testcontainers)
Architectural patterns & design principles
• Layered (Controller → Service → Repository)
• Dependency Injection (constructor injection of repository into controller/service)
• Domain-driven design (PizzaOrder entity encapsulates order state)
• Testcontainers for integration testing in CI (isolated DB per test suite)
Technologies & frameworks
• Java 21, Spring Boot 3.5+
• Spring Web (REST controllers)
• Spring Data JPA + Hibernate
• H2 (dev) / PostgreSQL (prod & tests)
• Testcontainers for isolated DB testing
• Maven (build, dependency resolution)
• Docker Compose (compose.yaml)