How mateustassinari/api-soccer-championships works
projectRestPuc is a Kotlin/Spring REST API for managing soccer teams, players, tournaments, matches, and transfers. Users authenticate to obtain a JWT, then call API endpoints to manage those records; match-event operations also publish messages to RabbitMQ, while match events are stored in MySQL. The graph preserves the documented domain capabilities and the sampled controller/service boundaries. Several implementations and integrations are unsampled, so their internal call paths are not inferred.
Main entry points: MatchController.kt Match API · PlayersController.kt Players API · EventService.kt Match events · services Tournament service
Components 19
API and security
- Authentication API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/AuthController.kt - JWT security
src/main/kotlin/br/com/mateus/projetoRestPuc/security
Soccer management
- Teams API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TeamsController.kt - Players API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/PlayersController.kt - Tournament API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TournamentController.kt - Match API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/MatchController.kt - Transfers API
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TransfersController.kt
Domain services
- Team service
src/main/kotlin/br/com/mateus/projetoRestPuc/services - Player service
src/main/kotlin/br/com/mateus/projetoRestPuc/services - Tournament service
src/main/kotlin/br/com/mateus/projetoRestPuc/services - Match service
src/main/kotlin/br/com/mateus/projetoRestPuc/services - Transfer service
src/main/kotlin/br/com/mateus/projetoRestPuc/services - Match events
src/main/kotlin/br/com/mateus/projetoRestPuc/services/EventService.kt
Persistence and messaging
- Domain entities
src/main/kotlin/br/com/mateus/projetoRestPuc/entities - JPA repositories
src/main/kotlin/br/com/mateus/projetoRestPuc/repositories - RabbitMQ sender
src/main/kotlin/br/com/mateus/projetoRestPuc/rabbit/QueueSender.kt
Other components
- API client
- MySQL
- RabbitMQ events queue
Connections 21
- API client → Authentication API: logs in
README.md - API client → JWT security: sends token
README.md - API client → Teams API: manages teams
README.md - API client → Players API: manages players
README.md - API client → Tournament API: manages tournaments
README.md - API client → Match API: manages matches
README.md - API client → Transfers API: manages transfers
README.md - Teams API → Team service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TeamsController.kt - Players API → Player service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/PlayersController.kt - Players API → Transfer service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/PlayersController.kt - Tournament API → Tournament service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TournamentController.kt - Match API → Match service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/MatchController.kt - Match API → Tournament service: checks tournament
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/MatchController.kt - Match API → Match events: records events
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/MatchController.kt - Transfers API → Transfer service: delegates to
src/main/kotlin/br/com/mateus/projetoRestPuc/controllers/TransfersController.kt - Team service → JPA repositories: uses team repository
src/main/kotlin/br/com/mateus/projetoRestPuc/services/impl/TeamServiceImpl.kt - Tournament service → JPA repositories: uses repositories
src/main/kotlin/br/com/mateus/projetoRestPuc/services/impl/TournamentServiceImpl.kt - JPA repositories → MySQL: persists records
- Match events → MySQL: stores match events
README.md - Match events → RabbitMQ sender: publishes events
README.md - RabbitMQ sender → RabbitMQ events queue: sends messages
README.md