Closed Alpha
FluxPlay is currently in Closed Alpha. This documentation is a work in progress and may be incomplete or out of date. Features, UI, and APIs are subject to change without notice. For access inquiries, please contact [email protected].
SYSTEM ARCHITECTURE
FluxPlay is built on a modern, decoupled monolithic architecture designed for high throughput and modular extensibility.
The Presentation LayerReact 18 / Tailwind / Vite
A responsive SPA handling user interaction, state management (Abstractions/Zustand), and media rendering. Communicates strictly via REST/WS.
The API LayerASP.NET Core 8 / SignalR
High-performance middleware handling Authentication, Authorization (RBAC), and Request Validation. Routes traffic to core services.
The Service LayerC# Business Logic
The brain of FluxPlay. Contains the Media Scanner, Metadata Engine, Transcoding Orchestrator, and Subscription Manager.
The Persistence LayerPostgreSQL / EF Core / Redis
Distributed data storage. Relational data sits in Postgres, while hot state (sessions, transcoding progress) lives in Redis.
Core Technologies
Design Principles
- Stateless API: No server-side session state (JWT only) for horizontal scaling.
- Event-Driven: Asynchronous tasks (scanning, notifications) are decoupled via background queues.
- Clean Architecture: Strict separation of concerns to prevent dependency loops.