How carlreid/streammaster works
Major system components
• Frontend (StreamMaster.WebUI): Built with React and TypeScript. This layer includes all the UI components, state management (Redux), hooks, and routing logic. It communicates with backend APIs (HTTP/REST) and uses SignalR for real-time notifications.
• API & Application Layer (e.g., StreamMaster.API, StreamMaster.Application): The entry point for client requests. It hosts controllers (for channels, EPG, schedules, settings, etc.) along with business logic and orchestration services.
• Domain Layer (StreamMaster.Domain): Contains the core business models, DTOs, enumerations, events, and shared utilities. This layer is central to defining the data and behaviors of the IPTV service.
• Infrastructure Layer (StreamMaster.Infrastructure, EF projects): Manages data access (repositories, EF migrations, PostgreSQL integration), external API integrations, caching, authentication, logging and other cross-cutting concerns.
• Additional Modules: There are specialized components such as:
• BuildClientAPI: Tools to generate client code for API integrations.
• EPG and SchedulesDirect modules: For managing electronic program guide (EPG) data and schedule synchronization.
• Streams and PlayList domains: Focusing on handling live streams and media playlist generation.
• WebSocket and SignalR components: For real-time messaging and proxying updates.
• External Services: Integration with public IPTV resources (via iptv-org list, tv-logos repositories) and potential media server integrations (Plex, Emby, Jellyfin).
Relationships and interactions between these components
• The Frontend sends HTTP (and web socket/SignalR) requests to the API layer.
• The API layer (controllers) calls into the Application layer to execute business operations.
• The Application layer, orchestrating use cases, manipulates domain objects from the Domain layer.
• The Domain layer encapsulates core business rules, and the Infrastructure layer provides persistence (via repository patterns) and additional services such as logging, caching, and authentication.
• Docker and container orchestration files (e.g., docker-compose.yml, Dockerfiles) indicate that the deployment is containerized, so include a container boundary around the complete system.
Architectural patterns and relevant technologies
• Layered (n-tier) architecture: Separate the UI, API/controllers, application logic, domain, and infrastructure.
• Domain Driven Design: Central Domain models with supporting Application Services.
• Use of modern web technologies: React/Redux for the front end and .NET (with C#) for backend services.
• SignalR is used for real-time communications.
• Entity Framework (EF) with PostgreSQL migrations in the Infrastructure layer.
• Docker containerization for consistent deployments.
Elements
• Clearly labeled components for:
• User / Client interface (browsers/mobile)
• Frontend (StreamMaster.WebUI with subcomponents for routing, state management, UI elements)
• API/Backend layer (StreamMaster.API controllers, endpoints for authentication, channel management, EPG management, etc.)
• Application/Service layer (StreamMaster.Application) handling orchestration and business logic
• Core Domain (StreamMaster.Domain) where the business entities and models reside
• Infrastructure (EF repositories, logging services, authentication, caching, and services for external integrations)
• Specialized modules (EPG, SchedulesDirect, Streams, PlayList)