How sevdesakar/companyexpensetracking works
Project Type and Purpose
• This is a layered .NET 8.0 Web API for a Company Expense Tracking application.
• It implements a clean-architecture style:
• CompanyExpenseTracking.Domain: core entities (Users, Expense, Category)
• CompanyExpenseTracking.Application: business logic / service interfaces
• CompanyExpenseTracking.Infrastructure: EF Core DbContext, JWT config, Redis & Hangfire integration
• CompanyExpenseTracking.API: REST controllers, validators, migrations, Swagger, authentication
• CompanyExpenseTracking.Tests: xUnit unit tests
File-Structure Analysis
• Top-level solution (CompanyExpenseTracking.sln) contains five projects:
• .Domain – entity definitions
• .Application – use-case/services layer
• .Infrastructure – data access & external infra (SQL via EF, JWT, Redis, Hangfire)
• .API – presentation layer (Web API controllers, HTTP endpoints, Swagger)
• .Tests – automated unit tests
• Key indicators:
• Controllers folder: REST resources (Auth, User, Expense, Category, Reports)
• DbContext folder in both .API and .Infrastructure: application-level vs shared data context
• Migrations folder: EF Core Code-First schema evolution
• Validators: FluentValidation rules for incoming models
• appsettings.json + launchSettings: environment & hosting configs
• Background jobs: Hangfire dashboard integrated in API
• Redis cache config: performance optimization layer
README Insights
• Feature highlights: JWT auth, role-based authorization, CRUD operations, background jobs (Hangfire), Redis caching, Swagger docs, xUnit tests
• Technology stack mapped directly to your layers
a. Main Components
1) External Clients – Web/Mobile UI, Postman/Swagger UI
2) API Gateway / Web API (CompanyExpenseTracking.API)
3) Authentication & Authorization (JWT middleware)
4) Controllers & Endpoint Layer
5) Application Services (CompanyExpenseTracking.Application)
6) Domain Model (CompanyExpenseTracking.Domain)
7) Infrastructure Services:
• SQL Database (via EF Core migrations)
• Redis Cache
• Hangfire Server & Dashboard
8) Unit Tests (for Application & Domain logic)
b. Relationships & Data Flows
• Client → HTTP(S) → API Controllers
• Controllers → validate (Validators) → invoke Application Services
• Application Services → enforce business rules → manipulate Domain entities
• Repositories in Infrastructure layer → EF Core DbContext → SQL Database
• Caching calls: Application Services ↔ Redis
• Background tasks: Application Services schedule jobs with Hangfire → Hangfire Server
• JWT Middleware sits on the API pipeline: intercepts requests, issues tokens on AuthController, enforces roles
c. Architectural Patterns & Principles
• Layered / Clean Architecture: strict dependency from API → Application → Domain → Infrastructure
• CQRS-style separation (commands for create/update, queries for read) can be highlighted if implemented
• Dependency Injection for services & repositories
• Code-First Migrations for schema evolution
• Background processing via Hangfire (fire-and-forget, delayed, recurring jobs)
• Redis used as a distributed in-memory cache
d. Key Technologies & Frameworks
• .NET 8 Web API (ASP.NET Core)
• Entity Framework Core (Code-First)
• Hangfire (with Dashboard)
• StackExchange.Redis
• JWT Bearer Authentication
• Swagger / Swashbuckle
• xUnit (unit testing)