How a Distributed Family Finance System Simplifies Home Budget Management
This article describes a distributed family finance system that centralizes scattered financial data across multiple platforms, detailing its Spring Cloud micro‑service backend, Node.js/Ant Design Pro frontend, architecture diagram, technology stack, module breakdown, functional features, and microservice segmentation for comprehensive household financial management.
Introduction
The distributed family finance system is a classic information‑management solution designed to centralize fragmented household consumption and investment data from various online platforms, enabling family members to manage assets more efficiently and conveniently.
Backend Architecture
The backend is built with MySQL and Java, leveraging a Spring Cloud micro‑service architecture to implement user, income/expense, stock, fund, asset, debt, and monthly/annual report services.
Frontend Implementation
The frontend uses Node.js and Ant.Design Pro to provide user‑friendly interactions, allowing operations such as recording and visualizing household income and expenses, dynamic stock and fund queries with charts, managing purchased assets, and generating month‑end and year‑end financial reports.
Architecture Diagram
Technology Stack
Static web server: Nginx‑1.14.2
Application server: Apache‑Tomcat‑8.5.59
Relational database: MySQL‑5.7.30
Non‑relational database: Redis‑6.0.8
Java version: 1.8.0_251
Frameworks: Spring Boot‑2.0.7, Spring Cloud‑Finchley.SR2
Message middleware: RabbitMQ‑3.4
Build tool: Maven‑3.6.3
Frontend language: React‑16.0.19
UI framework: Ant.Design‑Pro‑4.0.0
Chart library: Echarts‑For‑React‑2.0.16
Module Division
Expense overview (daily/monthly/yearly) with trend charts
Income overview (monthly/yearly) with trend charts
Stock market trends
Fund market trends
Purchased stocks (CRUD)
Purchased funds (CRUD)
External debt/credit management
Fixed assets (mortgages, loans, cash assets)
Month‑end report
Year‑end report
Sample Pages
Expense display:
Expense details:
Stock ranking:
Stock classification:
Stock details:
Asset statistics:
Debt situation:
Functional Overview
Expense Management
Displays daily/monthly/yearly expense curves, pie charts for expense categories (default monthly), and a CRUD table with filters for time range, type, and keywords.
Income Management
Shows total current month income (optional yearly), income trend curves, income category proportion charts, and a CRUD table with similar filters.
Stock Module
Provides stock rankings, detailed stock information, industry sectors, and CRUD operations for purchased stocks.
Fund Module
Offers fund rankings with filters by type, company, duration, scale, and growth, plus CRUD for purchased funds.
Fixed Assets
Displays mortgage and loan repayment status categorized by asset type.
Debt & Credit
Manages debt and credit records, sortable by type, person, and date.
Month‑End Report
Summarizes monthly income/expense, stock/fund transactions, profit/loss, and compares with the previous day; optionally sends a total asset summary via email.
Year‑End Report
Extends month‑end reporting to an annual overview.
Microservice Segmentation
User Service
Handles login and authentication (not included in the open‑source version).
Income/Expense Service
Manages income and expense data.
Stock/Fund Service
Processes stock and fund information.
Fixed Assets & Debt Service
Manages assets, mortgages, loans, and debt records.
Report Service
Generates various financial reports (not included in the open‑source version).
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
