HA monogram logoHandyana S. Atmaja
Back to ProjectsFull-Stack Application

Expense Tracker

A personal finance application designed to manage users, categories, transactions and monthly financial reports while demonstrating maintainable .NET application architecture.

View on GitHubIn development · paused
expense-tracker

Monthly balance

€2,430.00

Income

€3,800

Expenses

€1,370

Recent transactionsView all
Groceries•••
Salary•••
Internet•••
.NET 10ASP.NET CoreReactEF CorePostgreSQLFluentValidationJWTDockerxUnitMoqVerify
01 — Overview

Why I built it

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.

02 — Architecture

Feature-based Clean Architecture

The backend is separated into Domain, Application, Infrastructure and API layers while application functionality is organized around features rather than large technical folders.

Domain

Core business entities and rules without dependencies on infrastructure.

Application

Feature-based use cases, DTOs, validation and application contracts.

Infrastructure

EF Core, PostgreSQL repositories, authentication and external concerns.

API

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

03 — Features

Core functionality

The application currently focuses on the core functionality required for managing personal financial data securely and consistently.

User registration and login
JWT-based authentication
Category management
Income and expense transactions
Transaction ownership validation
Monthly financial reports
Request validation
Consistent ProblemDetails responses
04 — Technical Decisions

Engineering choices

Vertical Slice

Features keep endpoints, validation and application behavior close to the functionality they implement rather than organizing everything only by technical type.

JWT Authentication

Authentication is handled using JWT bearer tokens with user ownership checks protecting categories and transactions.

PostgreSQL + EF Core

PostgreSQL provides the relational datastore while EF Core handles persistence, migrations and repository implementations.

05 — Testing

Automated tests as part of the design

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.

06 — Next Steps

From backend project to cloud application

The backend is the foundation. The next stage is to add the frontend and deploy the complete application as a live portfolio project.

Build the React frontend
Add Docker-based application deployment
Deploy the API to Azure Container Apps
Provision infrastructure using Terraform
Create GitHub Actions CI/CD
Add OpenTelemetry-based observability

Interested in the implementation?

Explore the source code, architecture and development history on GitHub.

View Repository