How 51bitquant/howtrader works
Project type and purpose
• HowTrader is a Python‑based, event‑driven quantitative trading framework (forked and enhanced from VNPY).
• It provides a desktop GUI (PyQt), a plugin‑style set of “apps” (CTA strategies, algo trading, data management, recording, portfolio, risk, spread trading, TradingView integration), exchange gateways (REST + WebSocket), and a lightweight HTTP server for webhook (TradingView) signals.
Key architectural layers & top‑level components
A. User Interface Layer
• PyQt GUI – MainWindow, widgets under howtrader/trader/ui
• Flask HTTP server – webhook endpoint for TradingView (main() spawns a Flask app listening on /webhook)
B. Event & Core Engine Layer
• EventEngine – centralized pub/sub message bus (howtrader/event/engine.py)
• MainEngine – orchestrates gateways & apps (howtrader/trader/engine.py)
C. Gateway & API Adapters
• REST client (howtrader/api/rest/rest_client.py)
• WebSocket client (howtrader/api/websocket/websocket_client.py)
• Exchange gateways – Binance (spot/future/inverse), OKX (howtrader/gateway/*)
D. Application (Plugin) Layer
• CTA Strategy App (howtrader/app/cta_strategy)
• Algo Trading App (howtrader/app/algo_trading)
• DataManager, DataRecorder, PortfolioManager, PortfolioStrategy, RiskManager, SpreadTrading, TradingView apps
• Each app contains: engine, base template, UI widgets, specific strategy modules
E. Data Layer
• Database connectors – SQLite, MongoDB, MySQL (howtrader/trader/dbconnectors)
• Object models – OrderData, TradeData, ContractData with high‑precision Decimal (howtrader/trader/object.py)
• Charting & historical data retrieval (howtrader/chart)
Relationships & interactions
• GUI and HTTP server → publish user actions or incoming webhook as Event → EventEngine
• EventEngine → dispatch events to MainEngine
• MainEngine → routes market‑data events from Gateways → Apps/Strategies
• Strategies in Apps → generate orders (OrderData) → MainEngine → route to Gateways
• Gateways → send REST/WebSocket requests to external exchange APIs → receive fills/trades → push back as Events
• MainEngine → persists data via Database connectors → DataRecorder App/UI
• Backtesting loop: BacktestingEngine → loads historical bars from DB → drives strategy logic offline
Architectural patterns & design principles
• Event‑driven pub/sub core (decouples modules)
• Plugin architecture (“apps” can be added/removed at runtime)
• Adapter pattern for different gateways & databases
• Layered separation: UI, Core, Adapters, Data
• Single‑responsibility per module (each app only manages its domain)