eae3c31e53
Patterns applied: - Pattern 2: Float comparison (2x: utils.rs, var_edge_cases_tests.rs) - Pattern 7: Date/time construction (2x: production_streaming.rs, streaming.rs) - Pattern 1: Duration/time ops (2x: rate limiter, semaphore) - Pattern 4: Optional field access (1x: position_tracker.rs) Changes: - data/src/utils.rs: Float sort with NaN handling - data/src/providers/benzinga/production_streaming.rs: Rate limiter + semaphore + date/time - data/src/providers/benzinga/streaming.rs: Date/time construction - risk/src/position_tracker.rs: Emergency fallback counter - risk/tests/var_edge_cases_tests.rs: Test helper float sort Test impact: 0 failures (182/182 passing) Compilation: Clean (0 errors, 0 warnings) Time: 25 min (44% under budget)
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.