How singingsandhill/coinbot works
High-Level Architecture Overview
• CoinBot (Cryptocurrency Trading Service)
• Running Crew Archive (Running Management Service)
Application Layer (DTOs)
• Trading-related DTOs (Account, Market, OrderBook, etc.)
• Running-related DTOs (RunnerDistance, RunningRecord)
Domain Layer (Services)
• Trading Domain:
• Chart Service
• Candle Service
• Order Service
• Trading Service
• Technical Indicator
• Running Domain:
• Run Service
• Image Text Service
• Stock Service
Infrastructure Layer
• Repositories:
• Order History Repository
• Regular Repository
• Running Records Repository
• Trading Signal History Repository
• Stock Repository
Global Components
• Configuration (AppConfig, SecurityConfig, SwaggerConfig)
• Error Handling
• Schedulers (TradingScheduler)
B. External Integrations:
• Database (JPA/Hibernate)
• Web Interface (Templates)
• Static Resources (CSS/JS/Images)
Key Architectural Patterns to Highlight
• Layered Architecture (Controller → Service → Repository)
• Domain-Driven Design (separate domains for trading and running)
• MVC Pattern (for web interface)
• Repository Pattern (for data access)
• DTO Pattern (for data transfer)
Technical Details
• Spring Boot as the main framework
• JPA for database access
• Security configurations
• Scheduled tasks for trading bot
• Static resource handling
• Error handling mechanism