How lazarito444/proyecto-final-tds works
Project Type and Purpose
• This is a full-stack personal-finance management platform (“FinancIA”) with three clients (Web, Mobile, HTTP clients) and a layered ASP.NET Core backend exposing REST endpoints, real-time channels, and async messaging.
• The goal is to let users register, record transactions, view dashboards, set goals, and receive AI-powered recommendations and alerts.
Main Components
a. Clients
• Web App (Next.js + React): pages for login, signup, dashboard, transactions.
• Mobile App (Flutter): modules for auth, dashboard, transactions, onboarding.
• HTTP Client (Postman/Swagger – FinancIA.Api.http) for manual testing.
b. API Backend (ASP.NET Core)
• FinancIA.Api (Controllers, JWT authentication, SignalR hubs)
• FinancIA.Core.Application (DTOs, service interfaces, mapping, JwtService)
• FinancIA.Core.Domain (Entities: User, Role, Transaction, Category)
• FinancIA.Infrastructure.Persistence (EF Core DbContext, Configurations, Migrations)
c. Data Stores and Services
• SQL Server (ApplicationContext → Category, Transaction tables)
• RabbitMQ broker for background processing (e.g., bulk imports, notification tasks)
• SignalR Hub for pushing real-time alerts to Web/Mobile
• External OAuth providers (Google, Apple)
• AI/ML Service (classification, recommendations) – could be an internal microservice or external API
Relationships and Data Flows
• Web/Mobile clients → HTTP/HTTPS → ASP.NET Core API (JWT Bearer + OAuth flows)
• API → EF Core → SQL Server (synchronous reads/writes)
• API → RabbitMQ (publish events: transaction created, budget exceeded) → Worker/Subscriber → Database or Notification Service
• API ↔ SignalR Hub → real-time messaging to connected clients
• API → AI/ML Service (REST or gRPC calls) for classification and recommendations
• API → External OAuth Providers for social login
Architectural Patterns and Principles
• Layered (“Onion”/Clean) architecture: Controllers → Application Services → Domain Entities → Infrastructure
• Separation of concerns: Authentication, Business Logic, Persistence, Presentation are decoupled.
• Asynchronous messaging: decouple long-running tasks via RabbitMQ.
• Real-time updates: use SignalR for push notifications.
• DTO mapping: Automapper for translating between domain and transport models.
• Secure by design: JWT, OAuth, AES encryption, 2FA.
Technologies & Frameworks
• Backend: ASP.NET Core Web API, Entity Framework Core, SignalR, RabbitMQ .NET Client
• Database: SQL Server
• Web Frontend: Next.js (React + TypeScript), Axios for HTTP
• Mobile Frontend: Flutter (Dart), Dio for HTTP, shared themes/config
• CI/CD & Deployment: (if present) Dockerfiles, Kubernetes manifests, Azure/AWS pipelines