How ian-shepherd/reus works
Main Components
a. Data Sources Layer:
• FBref API Integration
• FotMob API Integration
• Transfermarkt API Integration
b. Core Library Components:
• Data Scraping Modules
• Data Processing Modules
• Utility Functions
c. Client Interface Layer:
• Public API Methods
• Documentation System
Architectural Pattern
[Client Applications]
• ↑
[Reus Public API]
• ↑
┌─────────────────────────────────────┐
• Core Modules │
• ┬─────────┬────────────────┤
• FBref │ FotMob │ Transfermarkt │
• Module │ Module │ Module │
• ┴─────────┴────────────────┘
• ↑
[Data Source APIs]
Component Details
a. For each data source module (FBref, FotMob, Transfermarkt):
• Separate submodules for different data types (matches, players, teams)
• Data transformation utilities
• Rate limiting and request handling
b. Utility Layer:
• Common functions
• Data processing helpers
• Error handling
Important Elements to Highlight
• Rate limiting mechanism (3-second delay between requests)
• Data transformation pipelines
• Error handling and retry logic
• Documentation system integration
Specific Module Relationships
• How the fbref module interacts with its submodules (fb_match_data, fb_team_data, etc.)
• How the fotmob module handles different data types (leagues, matches, stats)
• How the transfermarkt module manages player and team data