d8d51aa2d0
All 6 service Dockerfiles were missing newly-added workspace crates (web-gateway, ctrader-openapi, foxhunt-deploy, broker_gateway_service), causing cargo workspace resolution failures during Docker builds. Changes across all Dockerfiles: - Add COPY directives for web-gateway, ctrader-openapi, foxhunt-deploy, broker_gateway_service (new workspace members since Dockerfiles written) - Add SQLX_OFFLINE=true env and .sqlx cache copy where missing - Add perl and make system deps (needed for OpenSSL build from source) - Remove COPY migrations (dir excluded by .dockerignore, not needed) - Expand broker_gateway_service from 3-crate to full workspace copy Validated: docker build --check passes all 6, cargo check -p passes all 6. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Backtesting Service
Overview
The backtesting_service offers an independent and isolated environment for rigorously testing and validating trading strategies against historical market data. It provides a robust platform for simulating trading performance, analyzing strategy efficacy, and generating comprehensive performance reports before live deployment.
Features
- Independent Backtesting Service: Operates autonomously, allowing for parallel and isolated strategy evaluations.
- gRPC API for Backtest Execution: Exposes a clear API for submitting and managing backtesting jobs.
- Strategy Testing and Validation: Enables comprehensive testing of various trading strategies under different market conditions.
- Performance Reporting: Generates detailed reports including metrics like P&L, Sharpe ratio, drawdown, and win rate.
- Data Replay Engine: Accurately replays historical market data, simulating real-world order book dynamics and trade execution.
- Results Persistence: Stores backtesting results and reports for historical analysis and comparison.
gRPC API
The backtesting_service exposes a gRPC API for initiating and retrieving backtest results. Key endpoints include:
RunBacktest- Submit backtest configuration and strategyGetBacktestResults- Retrieve results for completed backtestsListAvailableStrategies- List registered strategiesGetBacktestReport- Get detailed performance report
Running the service
To run the backtesting_service binary:
cargo run --bin backtesting_service
Data Requirements
The service requires historical market data in Parquet format:
- Data should be stored in the configured data directory
- Supports tick data, order book snapshots, and OHLCV candles
- Data must include instrument, timestamp, and price/quantity fields
Testing
To run the tests for the backtesting_service crate:
cargo test --package backtesting_service
Documentation
Comprehensive API documentation is available at docs.rs/backtesting_service.