How rishabhchowkikar/finance-management-system works
Project type and purpose
• This is a full-stack, server-rendered web application built with Next.js (App Router) that provides a banking dashboard.
• Users can sign up/in, link their bank accounts (via Plaid), view balances and transaction histories, and transfer money (via Dwolla).
• It uses Appwrite as its backend-as-a-service (authentication & database), integrates external payment APIs (Plaid, Dwolla), and includes instrumentation (Sentry).
File structure
• app/
• (auth): sign-in & sign-up routes (server components + pages)
• (root): protected routes (my-banks, payment-transfer, transaction-history)
• layout.tsx: top-level layout & global styling (Tailwind)
• components/: reusable React UI components (bank cards, charts, forms)
• ui/: design system primitives (button, input, table, etc.)
• lib/actions/: “service layer” that encapsulates all API calls
• bank.actions.ts, transaction.actions.ts, user.actions.ts, dwolla.actions.ts
• lib/appwrite.ts, lib/plaid.ts: SDK wrappers & configuration
• constants/, types/: domain constants and TypeScript definitions
• instrumentation.ts(.client/.server): Sentry setup for edge & server environments
• next.config.ts, tsconfig.json, tailwind.config.js: build & linting configs
README for additional insights
• Indicates use of next/font, standard deploy on Vercel.
a. Main components (containers)
• Browser Client (Next.js React UI)
• Next.js Server / Edge Functions (Server Components & Server Actions)
• Service Layer (lib/actions)
• Appwrite (Auth & Database)
• Plaid API (Bank linking & data)
• Dwolla API (Payment transfers)
• Sentry (Error & performance monitoring)
b. Relationships & data flows
• User → Browser UI → Next.js server components → service layer → external services
• Service layer ↔ Appwrite for user & transaction data
• Service layer ↔ Plaid for bank data
• Service layer ↔ Dwolla for payment initiation
• Next.js edge functions report errors & metrics to Sentry
c. Architectural patterns
• Server-Side Rendering + Server Actions (Next.js App Router)
• Backend-for-Frontend (BFF) pattern via lib/actions
• Externalized services for auth, DB, payments, instrumentation
d. Key technologies
• Next.js (React, App Router, Server Components)
• Appwrite (backend-as-a-service)
• Plaid & Dwolla (external financial APIs)
• Tailwind CSS (utility styling)
• Sentry (monitoring)
• TypeScript