How jitterted/ensembler works
Main Components
a) External Interfaces:
• GitHub OAuth2 Authentication
• SendGrid Email Service
• Zoom API Integration
• Pushover Notification Service
• WebSocket Communication
b) Core Application Layers (following Hexagonal Architecture):
• Web Adapters (Controllers)
• Application Core (Domain & Services)
• Infrastructure Adapters (Repositories & External Services)
Architectural Pattern Representation
• Center: Domain Core (com.jitterted.mobreg.domain)
• Domain entities: Ensemble, Member, Timer
• Domain services and business logic
• Inner Ring: Application Layer (com.jitterted.mobreg.application)
• Port interfaces
• Application services
• Use cases
• Outer Ring: Adapters (com.jitterted.mobreg.adapter)
• Incoming adapters (Web controllers)
• Outgoing adapters (Repositories, External services)
Component Relationships
[External Users] → [GitHub OAuth] → [Web Controllers]
• ↓
[Web UI] ←→ [Controllers] → [Application Services] → [Domain Layer]
• ↓
• [Infrastructure Adapters]
• ↓
• [Database, Email, Zoom, Notifications]
Key Elements to Highlight
a) Authentication Flow:
• GitHub OAuth2 integration
• Member registration process
• Authorization checks
b) Core Features:
• Ensemble management
• Timer functionality
• Member registration
• Notification system
c) Data Flow:
• Repository patterns
• External service integration
• WebSocket communication
Technical Details
• Database: PostgreSQL (shown by migration files)
• Web Framework: Spring Boot
• Frontend: Thymeleaf templates with Tailwind CSS
• Real-time: WebSocket implementation
• Testing: Comprehensive test coverage with TestContainers