How priyanshu9898/expense-tracker-app works
Project Type and Purpose
• This is a full-stack MERN application for tracking and managing user expenses.
• Users interact via a React single-page application; the backend exposes a RESTful API (Node.js + Express); data is persisted in MongoDB; authentication uses JWT.
File Structure
• frontend/: React app
• public/: static HTML, manifest, robots.txt
• src/Pages/Auth, Avatar, Home: UI pages and forms
• src/components: reusable widgets (progress bars, spinner)
• src/utils/ApiRequest.js: API calls
• backend/: Express server
• Routers: route definitions (userRouter.js, Transactions.js)
• controllers: business logic (userController, transactionController)
• models: Mongoose schemas (UserSchema, TransactionModel)
• DB/Database.js: MongoDB connection setup
• app.js: main Express app with middleware (JWT auth)
README for Insights
• Confirms MERN stack, JWT-based auth, AWS Amplify hosting for frontend, Render for backend, CI/CD pipelines.
• Lists major features: user sign-up/login, CRUD on expenses/categories, dashboards with charts.
a. Components to include:
• User’s Browser (React SPA)
• Frontend Hosting (AWS Amplify)
• HTTP/S Client (Axios calls via ApiRequest.js)
• Backend API (Express server on Render)
– Routers → Controllers → Models → Database Layer
• Authentication Middleware (JWT verification)
• MongoDB (Atlas)
• External Libraries (tsparticles, react-datepicker)
• CI/CD Pipeline (GitHub → AWS/Render)
b. Interactions / Data Flows:
1. User → React UI (login, form submit)
2. React → HTTP requests → Express endpoints
3. Express JWT middleware validates token → controllers
4. Controllers call Mongoose models → MongoDB
5. DB responds → controllers → routers → React
6. React renders updated UI (charts, tables)
c. Architectural Patterns:
• Layered Architecture (Presentation → API → Service/Controller → Data)
• MVC-like in backend (Routers = C, Models = M, Controllers = V/logic)
• Client-server separation, RESTful API
d. Key Technologies:
• Backend: Node.js, Express.js, JWT, Mongoose
• Database: MongoDB Atlas
• Deployment: AWS Amplify (frontend), Render (backend)
• CI/CD: GitHub Actions or similar
Essential Details
• Middleware layer for JWT token verification.
• Environment variables (MONGO_URL, PORT).
• Configuration module (Database.js) initializing the DB connection.
• Core endpoints (e.g., POST /api/auth/login, GET /api/transactions).
• Use of third-party libraries where they affect architecture (tsparticles for UI effect).