How martinellich/jtaf4 works
Main System Components
a. Frontend Layer:
• Vaadin-based UI components (found in src/main/java/ch/jtaf/ui)
• Main views (Dashboard, Athletes, Clubs, Events, etc.)
• Theme components (src/main/frontend/themes/jtaf)
b. Application Layer:
• Security components (src/main/java/ch/jtaf/configuration/security)
• Domain services (src/main/java/ch/jtaf/domain)
• Reporting system (src/main/java/ch/jtaf/reporting)
c. Data Layer:
• Database (PostgreSQL, evident from scripts/start_postgres.sh)
• Data Access Objects (all *DAO.java files)
• Database migrations (src/main/resources/db/migration)
Key Architectural Elements
a. Core Business Components:
• Competition management
• Results calculation system
• Ranking services
• User management
• Organization management
b. Integration Points:
• Security integration
• IAAF formula integration for points calculation
• Reporting system
Component Relationships
Key interactions:
[Web Browser] → [Vaadin UI Layer]
• ↓
[Security Layer] ← → [Application Services]
• ↓
[Domain Services] → [Data Access Layer] → [PostgreSQL Database]
• ↓
[Reporting System]
Technical Stack Indicators
Technologies:
• Vaadin (UI Framework)
• Spring Boot (Application Framework)
• jOOQ (Database Access)
• Flyway (Database Migrations)
• PostgreSQL (Database)
Deployment Context
Deployment-related components:
• Docker container support (Dockerfile)
• Cloud deployment readiness (fly.toml)
• CI/CD pipeline (.github/workflows)
This architecture reflects a modern web application with clear separation of concerns, robust security, and scalable design suitable for managing track and field competitions.