Expense Tracker Three Tier

A full-stack expense tracking web application built with React, Node.js, and PostgreSQL. Features JWT authentication, expense CRUD operations, dashboard analytics with charts, and CSV export functionality.

reactjsnodejskuberneteseksingress

Architecture

This application follows a three-tier architecture:

Tier 1 - Frontend: React.js application with Tailwind CSS Tier 2 - Backend: Node.js REST API with Express and JWT authentication Tier 3 - Database: PostgreSQL with Sequelize ORM

📁 Directory Structure

app/
├── frontend/          # React frontend application
├── backend/           # Node.js API server
├── database/          # Database migrations and seeders
└── README.md          # This file

Note:

This repository contains a three-tier application built with the help of AI agents, designed to practice real-world deployment workflows. The project focuses on:

  • Containerizing applications using Docker
  • Deploying workloads on Kubernetes (EKS)
  • Managing frontend, backend, and database layers
  • Configuring Ingress with a custom domain
  • Securing traffic using TLS certificates (Let’s Encrypt)
  • Applying Kubernetes best practices such as namespaces, config maps, secrets, jobs, and services
  • The primary goal of this project is to gain hands-on experience with production-like Kubernetes deployments, cloud-native architecture, and infrastructure automation.

K8s infra Directory Structure

.
├── .gitignore
├── README.md
│
├── namespace.yaml
│   # Kubernetes namespace for isolating application resources
│
├── configmap-backend.yaml
├── configmap-frontend.yaml
│   # Application configuration for backend and frontend
│
├── secret-backend.yaml
│   # Sensitive backend credentials (DB, secrets, etc.)
│
├── deployment-backend.yaml
├── deployment-frontend.yaml
│   # Kubernetes Deployments for backend and frontend services
│
├── service-backend.yaml
├── service-frontend.yaml
│   # ClusterIP services exposing backend and frontend internally
│
├── ingress.yaml
│   # Ingress resource for routing traffic via custom domain
│
├── lets-encrypt-cert.yaml
│   # TLS certificate configuration using Let’s Encrypt
│
├── db-migrate-job.yaml
│   # Kubernetes Job for database migrations
│
├── iam-policy.json
├── iam_policy.json
├── trust-policy.json
│   # IAM and trust policies used for AWS EKS integrations
View on GitHub
Loading similar projects...