# denmette/pizza-kata architecture

> Architecture diagram of the GitHub repository denmette/pizza-kata, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-07-25). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/denmette/pizza-kata
- Repository: https://github.com/denmette/pizza-kata

## Overview

##### 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)

## Diagram (Mermaid)

```mermaid
flowchart TB
    %% External Client
    Client["Client (curl/Postman)"]:::external

    %% Build & Dependency Management
    Build["Maven CLI"]:::orchestration

    %% Orchestration
    DC["Docker Compose"]:::orchestration
    TC["Testcontainers"]:::orchestration

    %% Databases
    DBH2["H2 (in-memory)"]:::db
    DBPG["PostgreSQL (container)"]:::db

    %% Application Boundary
    subgraph "Spring Boot Application"
        direction TB
        App["PizzaKataApplication"]:::app
        OC["OrderController"]:::app
        Svc["Business Service"]:::app
        Repo["PizzaOrderRepository"]:::app
        EM["PizzaOrder (JPA Entity)"]:::app
        Config["application.properties"]:::app
        SchemaSQL["schema.sql"]:::db
        DataSQL["data.sql"]:::db
    end

    %% Data Flows
    Client -->|HTTP POST /order| OC
    OC -->|"calls service"| Svc
    Svc -->|"uses repository"| Repo
    Repo -->|JDBC| DBH2
    Repo -->|JDBC| DBPG
    DC --- DBPG
    DC --- App
    TC --- DBPG
    TC --- App

    %% Build flows
    Build --> App

    %% Click Events
    click App "https://github.com/denmette/pizza-kata/blob/trunk/src/main/java/be/pizza/kata/PizzaKataApplication.java"
    click OC "https://github.com/denmette/pizza-kata/blob/trunk/src/main/java/be/pizza/kata/OrderController.java"
    click EM "https://github.com/denmette/pizza-kata/blob/trunk/src/main/java/be/pizza/kata/PizzaOrder.java"
    click Repo "https://github.com/denmette/pizza-kata/blob/trunk/src/main/java/be/pizza/kata/PizzaOrderRepository.java"
    click Config "https://github.com/denmette/pizza-kata/blob/trunk/src/main/resources/application.properties"
    click SchemaSQL "https://github.com/denmette/pizza-kata/blob/trunk/src/main/resources/schema.sql"
    click DataSQL "https://github.com/denmette/pizza-kata/blob/trunk/src/main/resources/data.sql"
    click DC "https://github.com/denmette/pizza-kata/blob/trunk/compose.yaml"
    click Build "https://github.com/denmette/pizza-kata/blob/trunk/pom.xml"
    click Build "https://github.com/denmette/pizza-kata/tree/trunk/./mvnw"
    click Build "https://github.com/denmette/pizza-kata/blob/trunk/./mvnw.cmd"
    click Build "https://github.com/denmette/pizza-kata/blob/trunk/.mvn/wrapper/maven-wrapper.properties"
    click README "https://github.com/denmette/pizza-kata/blob/trunk/README.md"
    click Tests1 "https://github.com/denmette/pizza-kata/blob/trunk/src/test/java/be/pizza/kata/OrderControllerTest.java"
    click Tests2 "https://github.com/denmette/pizza-kata/blob/trunk/src/test/java/be/pizza/kata/PizzaKataApplicationTests.java"

    %% Styles
    classDef app fill:#E8F1FF,stroke:#1E70BF,color:#000
    classDef db fill:#E6F4EA,stroke:#238636,color:#000
    classDef orchestration fill:#FFF4E5,stroke:#D97706,color:#000
    classDef external fill:#F0F0F0,stroke:#6B7280,color:#000
```
