How coder-pro10z/money-pilot works
Project Type and Purpose
• MoneyPilot is a full-stack, finance/productivity web application.
• Frontend: Angular SPA for expense tracking, budget planning, analytics.
• Backend: ASP.NET Core Web API (Clean Architecture) exposing secure endpoints, backed by SQL Server via EF Core.
File Structure
• Top-level “src” contains four .NET projects:
• MoneyPilot.API – Controllers, middleware, startup, HTTP file
• MoneyPilot.Application – DTOs, service & repository interfaces
• MoneyPilot.Infrastructure – EF Core DbContext, Migrations, Repositories, Services
• MoneyPilot.Domain – Entities, value objects, enums
• Tests in MoneyPilot.Tests (xUnit) exercising Controllers.
• Config files: appsettings.json, launchSettings.json.
• Migrations folder reflects EF Code-First approach.
README for Additional Insights
• System uses JWT/ASP.NET Identity for Auth.
• Clean Architecture / Layered design (Frontend → API → Application → Infrastructure → Domain → SQL DB).
• Angular 17, Chart.js/ngx-charts, Angular Material/Tailwind on the client.
• CI/CD via GitHub Actions/Jenkins, deployment targets Azure App Service/Netlify/Vercel.
Main Components & Boundaries
a. Client Layer
• Angular SPA running in the user’s browser
• Modules: Auth, Expenses, Budgets, Dashboard, Habits, Investments
b. API Layer
• MoneyPilot.API: Controllers (Auth, Expense, Budget, RecurringTransaction, Home)
• Middleware: JWT Authentication, Logging
• Extensions & Helpers (ClaimsPrincipalExtensions)
c. Application Layer
• Service interfaces (IBudgetService, IExpenseService, etc.)
• DTOs for input/output mapping
• Orchestrates business rules
d. Infrastructure Layer
• EF Core MoneyPilotDbContext (DbSets for Entities)
• Repositories (BudgetRepository, ExpenseRepository, generic Repository)
• UnitOfWork abstraction
• Domain services: RecurringTransactionService, AutoLoginTokenService, Test helpers
• Migrations for schema evolution
e. Domain Layer
• Core Entities (AppUser, Budget, Expense, RecurringTransaction, Category)
• BaseAuditableEntity and Enums (RecurrenceType)
f. Persistence
• SQL Server database
• EF Core Code-First migrations
g. External Services & DevOps
• JWT token issuer (ASP.NET Identity)
• Swagger/OpenAPI docs
• CI/CD pipelines (GitHub Actions, Jenkins, Octopus Deploy)
• Hosting: Azure App Service, Netlify/Vercel for frontend
Relationships and Data Flows
1. User in browser (Angular) invokes HTTP(S) → API
2. Controller receives request → validates/authenticates (JWT)
3. Controller calls Application Service via DI
4. Application Service uses UnitOfWork → Repository
5. Repository queries/updates SQL via DbContext
6. DbContext commits transaction → SQL Server
7. Data maps back up the chain through DTOs → Controller → Angular for UI update
Architectural Patterns & Principles
• Clean/Layered Architecture: strict separation of concerns
• Dependency Injection at each layer
• Repository + Unit of Work patterns for data access
• DTOs and AutoMapper for boundary mapping
• Code-First Migrations for schema management
• JWT/ASP.NET Identity for secure auth
• Testability: xUnit tests, mockable interfaces
Detailed Elements
• Angular modules and HTTP interceptor for JWT
• AuthController issuing tokens
• Expense & Budget Controllers → Application Services interfaces → Concrete Services in Infrastructure
• DbContext + Migrations aligned under Infrastructure
• UnitOfWork coordinating Repositories
• SQL Server (with EF Core) at the bottom
Detail
• Where AutoMapper, FluentValidation, Logging live (extensions/middleware)
• Asynchronous vs. synchronous flows if relevant (e.g., recurring transactions scheduler)