# aymenchla/tennis-score-computer architecture

> Architecture diagram of the GitHub repository aymenchla/tennis-score-computer, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-09-19). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/aymenchla/tennis-score-computer
- Repository: https://github.com/aymenchla/tennis-score-computer

## Overview

##### Project Type and Purpose
- This is a backend-focused Kagata “kata” application—a Tennis Score Computer—built with Java, Maven, and Spring Boot, following a Hexagonal (Ports & Adapters) architecture.
- Its goal is to compute and output the current score of a tennis game based on inputs fed via CLI or Kafka, and print results to the console.

##### File Structure Analysis
Top-level:
- pom.xml, mvnw* – Maven build & wrapper files.
- src/main/java/com/kata/tennis_score_computer – main codebase, organized into:
– adapter/input/cli (TennisGameCliAdapter)
– adapter/input/kafka (TennisGameKafkaConsumer)
– adapter/output/console (TennisScoreConsolePrinter)
– application/service (TennisGameUseCaseImpl)
– domain/model (Player, Score, TennisGame)
– domain/port/input (PlayTennisGameUseCase)
– domain/port/output (ScoreOutputPort)
– config (TennisGameRunnerConfig)
- src/main/resources/application.properties – Spring Boot config.
- src/test – matching unit and integration tests.

##### README Insights
- Minimal description, but repository name and module naming confirm this is a Tennis Score Computer Kata.

##### Components
a. Main Components
- Adapters/Input
– CLI Adapter
– Kafka Consumer Adapter
- Application Layer
– TennisGameUseCaseImpl (implements input port)
- Domain Layer (Core)
– TennisGame, Player, Score (domain model)
– PlayTennisGameUseCase (input port interface)
– ScoreOutputPort (output port interface)
- Adapters/Output
– Console Printer
- Configuration & Runner
– TennisGameRunnerConfig (Spring Boot wires up adapters and use-case)
- External Systems
– STDIN/Console
– Kafka Broker

b. Relationships & Data Flows
1. User or external system → Input Adapter (CLI/Kafka)
2. Adapter calls → PlayTennisGameUseCase (port)
3. Flow into Application Service → domain model (TennisGame.play, update Score)
4. Application invokes → ScoreOutputPort → Output Adapter (ConsolePrinter)
5. Output Adapter emits → STDOUT

c. Architectural Patterns & Principles
- Hexagonal / Ports & Adapters: clear separation between domain, application, and infrastructure.
- Dependency Inversion: domain and application layers depend on interfaces (ports), not implementations.
- Single Responsibility: each adapter solves one I/O concern.

d. Key Technologies & Frameworks
- Java 17+ (assumed)
- Spring Boot (auto-configuration, dependency injection)
- Maven (build & dependency management)
- Kafka Client (for input)

## Diagram (Mermaid)

```mermaid
graph TD
  subgraph "External Systems"
    User["User (CLI)"]:::external
    KafkaBroker[(Kafka Broker)]:::external
    ConsoleIO["Console I/O"]:::external
  end

  subgraph "Adapters / Input"
    CLIAdapter["CLI Adapter"]:::adapter
    KafkaAdapter["Kafka Consumer Adapter"]:::adapter
  end

  subgraph "Application Layer"
    UseCase["TennisGameUseCaseImpl"]:::application
  end

  subgraph "Domain Layer"
    ITFIn["PlayTennisGameUseCase"]:::domain
    ITFOut["ScoreOutputPort"]:::domain
    TennisGame["TennisGame"]:::domain
    Player["Player"]:::domain
    Score["Score"]:::domain
  end

  subgraph "Adapters / Output"
    ConsolePrinter["Console Printer"]:::adapter
  end

  subgraph "Configuration & Runner"
    Config["TennisGameRunnerConfig"]:::config
    Entry["TennisScoreComputerApplication"]:::config
  end

  %% Relationships
  User --> CLIAdapter
  KafkaBroker --> KafkaAdapter
  CLIAdapter -->|"playGame()"| UseCase
  KafkaAdapter -->|"playGame()"| UseCase
  UseCase -->|"uses"| TennisGame
  UseCase -->|"uses"| Player
  UseCase -->|"uses"| Score
  UseCase -->|"invoke printScore()"| ConsolePrinter
  ConsolePrinter --> ConsoleIO
  Entry --> Config
  Config --> CLIAdapter
  Config --> KafkaAdapter
  Config --> UseCase
  Config --> ConsolePrinter

  %% Click Events
  click CLIAdapter "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/adapter/input/cli/TennisGameCliAdapter.java"
  click KafkaAdapter "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/adapter/input/kafka/TennisGameKafkaConsumer.java"
  click ConsolePrinter "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/adapter/output/console/TennisScoreConsolePrinter.java"
  click UseCase "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/application/service/TennisGameUseCaseImpl.java"
  click ITFIn "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/domain/port/input/PlayTennisGameUseCase.java"
  click ITFOut "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/domain/port/ouput/ScoreOutputPort.java"
  click TennisGame "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/domain/model/TennisGame.java"
  click Player "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/domain/model/Player.java"
  click Score "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/domain/model/Score.java"
  click Config "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/config/TennisGameRunnerConfig.java"
  click Entry "https://github.com/aymenchla/tennis-score-computer/blob/main/src/main/java/com/kata/tennis_score_computer/TennisScoreComputerApplication.java"

  %% Styles
  classDef external fill:#dff,stroke:#080,stroke-width:1px
  classDef adapter fill:#fdd,stroke:#f00,stroke-width:1px
  classDef application fill:#ddf,stroke:#00f,stroke-width:1px
  classDef domain fill:#eee,stroke:#333,stroke-width:1px
  classDef config fill:#ffd,stroke:#aa0,stroke-width:1px
```
