How jean-edouard-boulanger/finbot works
High-Level Architecture Components
The system should be represented as a multi-tier architecture with these main components:
a. Frontend Layer:
• React Web Application (webapp/)
• REST API interactions with backend
• Features: authentication, dashboard, reports, settings
b. Backend Services Layer (show as separate microservices):
• appwsrv (Main application API)
• finbotwsrv (Financial data fetching service)
• snapwsrv (Snapshot orchestration service)
• histwsrv (Financial reporting service)
• schedsrv (Scheduling service)
c. Data Providers Layer:
• External Financial Services (Plaid, Credit Agricole, Aegon, etc.)
• APIs (Kraken, Binance, etc.)
• Manual Input (Google Sheets)
d. Infrastructure Layer:
• PostgreSQL Database
• RabbitMQ (indicated by rmq.py)
• Docker containers
Interaction Flows
a. Data Flow:
• User interactions → Frontend → appwsrv
• schedsrv → finbotwsrv → External Providers
• snapwsrv orchestration flow
• histwsrv reporting workflow
b. Authentication Flow:
• Auth context and user session management
• Security boundaries
Key Components Detail
a. Core Services (Rectangle):
• Blue: Web Services
• Green: Data Processing Services
• Yellow: Scheduled Tasks
• Database
• Key-Value Store
c. External Systems (Cloud):
• Third-party Financial Providers
• APIs
Additional Elements
Include:
• Component types
b. Security Boundaries:
• Internal network
• External network
• Authentication zones
Implementation Details
Implementation aspects:
a. Technology Stack:
• Python Backend
• React Frontend
• SQLAlchemy ORM
• OpenAPI/Swagger Integration
b. Service Communication:
• REST APIs
• Message Queue
• Database Access
Deployment Context
Include:
a. Docker Container Boundaries:
• Service isolation
• Network segments
b. Environment Configuration:
• Development vs Production setup
• Configuration management
Monitoring & Operations
Include:
a. Health Checks:
• Service status monitoring
• Error handling
b. Data Flow Monitoring:
• Logging points
• Metrics collection
Remember to emphasize the self-hosted nature of the system and the security implications of handling financial credentials, as mentioned in the disclaimer.