How thamjianhao/fund-management-system works
Project type and purpose
• This is a monolithic Django REST Framework API for managing “fund” records (CRUD).
• The README describes RESTful endpoints (/funds/, /funds/<id>/), JSON data interchange, and an underlying SQL database (MySQL or SQLite).
File structure
• Top-level:
• manage.py (Django CLI)
• db.sqlite3 (default local DB)
• datadump.json (fixture)
• README.md
• funds/ (Django project and app combined—settings, wsgi, asgi)
• funds/ contains:
• settings.py, urls.py, wsgi.py, asgi.py → Django project configuration and entry points
• admin.py → Django admin registrations
• models.py → ORM definitions (Fund model)
• serializers.py → DRF serializers (Model↔JSON mapping)
• views.py → DRF viewsets or APIViews handling HTTP requests
• migrations/ → database schema evolution
• test.py → unit tests
• No separate “frontend” or microservices—single backend monolith.
Extract architecture clues from README
• Dependencies: Django, Django REST Framework, MySQL adapter (or SQLite fallback).
• Workflow:
• Client sends HTTP requests → Django URL router → DRF Views → Serializers → ORM → Database
• Admin panel as a side-component for data management.