How mantasdaskev/mediafon_tech_task works
Main Components
A. Frontend Layer (Angular):
• Login Component
• Submissions Component
• New Submission Component
• Services (API Service & State Hub Service)
• Models (Submission, Login, etc.)
B. Backend Layer (.NET Core):
• API Controllers (LoginController, SubmissionsController)
• SignalR Hub (SubmissionsStateHub)
• Business Logic Layer
• Data Access Layer
• Background Services
C. Database Layer:
• Main entities: Users and Submissions
Component Relationships and Interactions
A. Frontend-Backend Communication:
B. Backend Internal Flow:
• Layered architecture:
• Controllers → Business Logic → Data Access → Database
• Background Services → Business Logic
• SignalR Hub → Business Logic
Special Architectural Elements to Highlight
A. Real-time Updates System:
• Flow from SubmissionStateUpdater through SignalR to the client
• Queue-based update mechanism
B. Repository Pattern:
• Separation between business logic and data access
• Interface-based dependencies
C. Service Layer:
• Separation between controllers and business logic
• How services coordinate between different components
Additional Notes
• A title: "Mediafon Tech Task - System Architecture"
• Version/date information
• Notes about the authentication flow
• Real-time submission state update mechanism
• Separation of concerns between Core and Web projects
Technical Details
• Angular version
• .NET Core version
• SignalR for real-time communications
• Entity Framework Core for data access
• JWT authentication (if used)
• Database provider