How ptkr0/keipai works
• OAuth 2.0 for authentication (Google for YouTube, Twitch for streaming)
• MS SQL for the database along with Entity Framework Core migrations
• Azure Blob Storage for file (images) storage
• Real-time Twitch notifications via webhooks (with optional ngrok for local tunnel testing)
• External services like YouTube Data API v3 and Twitch API
• Frontend (Client Side):
– UI/UX: Indicate integration with Tailwind CSS and daisyUI.
• Backend (Server Side):
– Business Logic: Include “Services” and “Background Services” (e.g., TwitchAccountsBGService, YoutubeBGService, etc.) that process data and integrate with external APIs.
– Data Access Layer: Represent the Repositories and Entity Framework Core (ApplicationDBContext) which interact with the SQL Server.
• Database:
– SQL Server: Indicate MS SQL as the primary database, and optionally a note about SSMS for management.
• External Services & Integrations:
– OAuth 2.0 Services: Google Cloud (for YouTube) and Twitch Developers (for Twitch credentials).
– Azure Blob Storage: For storing images and file uploads.
– ngrok (optional): For tunnelling external notifications (especially Twitch webhooks) when running locally.
Out the Relationships & Data Flows
– The Angular application sends HTTP requests (e.g., REST API calls) to the .NET API endpoints.
• Within the Server, show:
– Controllers accepting HTTP calls and delegating tasks to the respective Services.
– Services managing business logic and calling into Repositories for CRUD operations.
– Background Services running asynchronously and integrating with external APIs (Twitch, YouTube) to fetch real-time data.
– Separation where additional supporting components (e.g., secure file uploads/Blob operations, token handling) are clearly indicated.
• For external integrations:
– Clearly label these as “External APIs/Services” with information flow (credential exchanges, content retrieval/update, file storage).
Architectural Patterns & Technologies
• Separation of concerns:
– The presentation layer (Angular client) is cleanly decoupled from the server’s API layer.
• Use of MVC-like patterns on the server side.
• Security aspects (JWT stored in cookies and OAuth flows).
• Real-time communication via Twitch webhooks.
Additional Notes
• Use descriptive text nodes to mention the specific technologies used (e.g., ".NET 8", "Angular 18", "Entity Framework Core", "MS SQL", "Tailwind CSS").