How konilo/purchasing-power works
Main Components
a. Data Sources Layer:
• Eurostat API
• US Bureau of Labor Statistics API
• REST Countries API
b. ETL Service:
• Separate modules for each data source (eurostat, usbls, restcountries)
• ETL processing flow
c. Data Storage:
• AWS RDS PostgreSQL Database
• Different schema layers (raw data vs. enriched data)
d. Enrichment Service:
• Data transformation flow
• Connection to database for both input and output
e. Backend Service:
• FastAPI server
• API endpoints (CPI, CPI correction, personal finances)
• Connection to enriched database schema
f. Frontend Service:
• React/Vite application
• Main components (Basics, PersonalFinance, About)
• Static hosting on AWS S3
Component Relationships
• Data ingestion flow: External APIs → ETL → Raw Database
• Data processing flow: Raw Database → Enrichment → Enriched Database
• Application flow: Frontend → Backend → Enriched Database
Specific Design Elements
• Rectangles for services
• Hexagons for external APIs
• Rounded rectangles for AWS services
• Blue: AWS services
• Green: Data processing services (ETL, Enrichment)
• Yellow: External APIs
• Purple: Application services (Frontend, Backend)
Additional Details
Technical annotations:
• Docker containers for each service
• Programming languages used (Python, JavaScript/React)
• Key libraries (FastAPI, Vite)
• Database schemas and tables
Deployment Context
Deployment locations:
• AWS EC2 for Backend
• AWS S3 for Frontend
• AWS RDS for Database
• Local machine for ETL and Enrichment services
User Interface
This layered approach will help maintain clarity while showing the complete system architecture. Remember to maintain consistent spacing and alignment for better readability.