How finmind/finmind-visualization works
Project type and purpose
• This is a data‐pipeline / microservices‐style backend system that ingests financial data from the external FinMind API, processes and stores it, then exposes it via REST endpoints and a lightweight visualization service. It also provides an analytics/dashboard layer via Redash.
File structure
• Top level: Docker orchestration (Dockerfile, make targets), environment configs (mysql.yml, rabbitmq.yml, redash.yml, finmind.yml, local.ini), Python packaging (setup.py, Pipfile).
• “visualization/”: core Python code
• api/v1: FastAPI endpoints for creating tables, syncing history, updating data
• backend/: application setup, routers, DB client, FinMind client
• scheduler.py: job scheduler that enqueues periodic tasks
• tasks/: Celery task definitions and worker bootstrap
• schema/: input schemas
• utility/: shared helper code
• tests/: unit tests for the task layer
README insights
• Services: MySQL, RabbitMQ (broker), Flower (monitoring), visualization (UI at :5000), finmind-visualization-api (FastAPI at :8888), Redash
• Make targets to spin up infrastructure and the FinMind sync API (with or without token)
Detail
• Side‐services (Flower monitoring)
• Retry / error‐handling loops if relevant (Celery retries)