How cgaswin/zenith works
Main Components
a. Microservices Architecture:
• Gateway Service (API Gateway)
• Eureka Registry Service (Service Discovery)
• Auth Service
• User Service
• Event Service
b. External Components:
• AWS S3 (for file storage, indicated by S3FileUpload classes)
• Database instances for each service
• Client Applications (implied by the API structure)
Component Relationships to Highlight
a. Client → Gateway:
• All client requests go through the gateway
• Security boundary
b. Gateway → Services:
• Route paths to appropriate services
• Load balancing indication
c. Services → Eureka Registry:
• Service registration
• Service discovery connections
d. Inter-service Communication:
• Auth Service → User Service (via Feign Client)
• Event Service → User Service (implied by JWT handling)
Specific Service Details
Auth Service:
• JWT authentication flow
• Security configurations
• User authentication endpoints
User Service:
• Athlete management
• Coach management
• Coaching relationships
• Request handling
Event Service:
• Event management
• Event registration
• Results tracking
• Item management
Additional Elements
Include:
• Security zones
• Load balancers
• Database connections
• Async communication patterns
• Service discovery paths
• JWT token flow
Technical Stack Indicators
Show:
• Spring Boot/Cloud usage
• Maven build system
• AWS integration
• Database types
• REST APIs