How aldowadsimanjuntak/banking-system works
Project Type and Purpose
• This is a full-stack banking system application.
• Frontend: Next.js (React) with TypeScript, Tailwind CSS, Axios.
• Backend: Express.js + Node.js, exposing RESTful endpoints for users, bank accounts, transactions, authentication, and media.
• Database: PostgreSQL accessed via Prisma ORM.
• Email service via Nodemailer, file uploads via Multer/imagekit, logging (Morgan), error tracking (Sentry), and API docs via Swagger/OpenAPI.
File Structure
• Top level:
• api/ – Express route handlers (BankAccount.js, Transaction.js, User.js, auth.js, media.js)
• controllers/ – Business logic separated from routes
• utils/ – Authentication helpers, JWT, file-upload, imagekit, middleware (require.login)
• nodemailer/ – Email templates and mailing code
• prisma/ – Schema and migrations for PostgreSQL
• router.js & index.js – Express app entrypoint and route registration
• openapi.json – Swagger spec for API docs
• tests/ & coverage/ – Jest test suites for controllers and endpoints
• banking-system-frontend/ – Next.js app with app-directory, services/api.ts, utils/auth.ts, pages for login/register/dashboard
• Patterns:
• Backend follows a layered MVC-style separation: routes (api/), controllers, utils/services.
• Frontend is organized per Next.js 14 conventions (app router, layout, page.tsx files, middleware for protected routes).
README for Additional Insights
• Tech stack section confirms frameworks and services.
• “Features” section highlights core modules (auth, accounts, transactions, dashboard).
• Running instructions reveal two servers: backend on port 3000, frontend on 3001.
• API docs accessible at /docs.