How mjsimo99/world-cup-2030-backend works
SatoCup appears to be a backend for managing a football cup: users and administrators authenticate, while clients can access competition, venue, team, match, and ticket functions. The tree shows REST controllers, service implementations, repositories, domain entities, and JWT security, but no README or source excerpts document their runtime interactions. The dashed links below therefore indicate likely architecture, not verified calls; the exact workflow and persistence configuration remain uncertain.
Main entry points: repository Repositories · impl Venue and team services · AdminAuthenticationController.java Admin authentication · ClientAuthenticationController.java Client authentication
Components 19
Access and security
- Admin authentication
src/main/java/com/example/satocup/controller/AdminAuthenticationController.java - Client authentication
src/main/java/com/example/satocup/controller/ClientAuthenticationController.java - JWT security
src/main/java/com/example/satocup/security - Admin API
src/main/java/com/example/satocup/controller/AdminController.java
Cup competition
- Match API
src/main/java/com/example/satocup/controller/MatchController.java - Team-match API
src/main/java/com/example/satocup/controller/TeamMatchController.java - Match services
src/main/java/com/example/satocup/service/impl/MatchServiceImpl.java - Team-match services
src/main/java/com/example/satocup/service/impl/TeamMatchServiceImpl.java
Venues and teams
- City API
src/main/java/com/example/satocup/controller/CityController.java - Stadium API
src/main/java/com/example/satocup/controller/StadiumController.java - Team API
src/main/java/com/example/satocup/controller/TeamController.java - Venue and team services
src/main/java/com/example/satocup/service/impl
Clients and tickets
- Client API
src/main/java/com/example/satocup/controller/ClientController.java - Ticket API
src/main/java/com/example/satocup/controller/TicketController.java - Ticket services
src/main/java/com/example/satocup/service/impl/TicketServiceImpl.java
Persistence and domain
- Repositories
src/main/java/com/example/satocup/repository - Domain entities
src/main/java/com/example/satocup/model/entity - Relational database
Other components
- User
Connections 24
- User → Admin authentication: authenticates
- User → Client authentication: authenticates
- Admin authentication → JWT security: uses tokens
- Client authentication → JWT security: uses tokens
- User → Match API: requests matches
- User → Team-match API: requests standings
- User → City API: requests cities
- User → Stadium API: requests venues
- User → Team API: requests teams
- User → Ticket API: requests tickets
- User → Client API: manages profile
- User → Admin API: administers
- Match API → Match services: delegates to
- Team-match API → Team-match services: delegates to
- City API → Venue and team services: delegates to
- Stadium API → Venue and team services: delegates to
- Team API → Venue and team services: delegates to
- Ticket API → Ticket services: delegates to
- Match services → Repositories: uses
- Team-match services → Repositories: uses
- Venue and team services → Repositories: uses
- Ticket services → Repositories: uses
- Repositories → Domain entities: maps data
- Repositories → Relational database: persists data