How medama-io/medama works
Main Components Identification
The system consists of three major components that should be prominently featured:
a) Tracker Component (/tracker)
• As a lightweight JavaScript module
• Integration with client websites
• Cookie-free nature
• Event capture functionality
b) Core Component (/core)
• Main server architecture
• Two database systems:
• DuckDB for analytics data
• SQLite for user management
• API endpoints (OpenAPI-based)
• Authentication system
c) Dashboard Component (/dashboard)
• React-based frontend
• Routing system
• Stats visualization components
• Settings management
Relationships and Data Flow
Website Visitors -> Tracker -> Core API -> DuckDB
• > SQLite
Dashboard UI <-> Core API (OpenAPI)
Detailed Component Breakdown
For each major component, include these elements:
Tracker:
• Event Collectors (page events, click events)
• Data API interface
• History tracking module
Core:
• API Layer (OpenAPI)
• Service Layer
• Database Layer
• DuckDB for analytics
• SQLite for user management
• Middleware (auth, CORS, error handling)
• Migration system
Dashboard:
• React Components
• API Client
• Stats Visualization
• Settings Management
Technical Stack Indicators
Technology labels:
• JavaScript/TypeScript (Tracker & Dashboard)
• Go (Core)
• DuckDB & SQLite (Databases)
• React (Dashboard)
• OpenAPI (API specification)
Deployment Context
Optional deployment scenarios:
• Single binary deployment
• Minimal resource requirements (256MB RAM)
• Container-based deployment (Docker)
Remember to include version information and any relevant notes about scaling considerations, as this appears to be a system that can handle both small websites and larger deployments.