Vertical Slice
Features keep endpoints, validation and application behavior close to the functionality they implement rather than organizing everything only by technical type.
A personal finance application designed to manage users, categories, transactions and monthly financial reports while demonstrating maintainable .NET application architecture.
Monthly balance
€2,430.00
Income
€3,800
Expenses
€1,370
The Expense Tracker is designed as more than a simple CRUD application. The goal is to demonstrate how I would structure a maintainable backend application using modern .NET practices.
The project separates business logic, application use cases, infrastructure and API concerns while keeping features grouped around the functionality they provide.
It also provides a foundation that can later be extended with a frontend, cloud deployment, CI/CD, observability and additional financial reporting capabilities.
The backend is separated into Domain, Application, Infrastructure and API layers while application functionality is organized around features rather than large technical folders.
Core business entities and rules without dependencies on infrastructure.
Feature-based use cases, DTOs, validation and application contracts.
EF Core, PostgreSQL repositories, authentication and external concerns.
ASP.NET Core Minimal API endpoints, authentication and HTTP concerns.
Client
React / Web App
API
ASP.NET Core
Application
Use Cases
Infrastructure
EF Core
Database
PostgreSQL
The application currently focuses on the core functionality required for managing personal financial data securely and consistently.
Features keep endpoints, validation and application behavior close to the functionality they implement rather than organizing everything only by technical type.
Authentication is handled using JWT bearer tokens with user ownership checks protecting categories and transactions.
PostgreSQL provides the relational datastore while EF Core handles persistence, migrations and repository implementations.
Application behavior is covered using xUnit with Moq for dependencies and Verify for snapshot-style assertions where appropriate. Authentication, category operations and transaction behavior are tested independently from the HTTP layer.
The backend is the foundation. The next stage is to add the frontend and deploy the complete application as a live portfolio project.
Explore the source code, architecture and development history on GitHub.
View Repository