How rameshkumar-cmd/nautilus_trader works
NautilusTrader is a Rust-native, event-driven trading system with Python as a control plane. A user configures strategies and orchestration, connects venue or data-provider adapters, and runs the system in backtest or live mode; both modes share strategy and execution semantics. The map includes market-data handling, portfolio/risk and persistence capabilities documented by the README, plus sampled internal layers. Several subsystems are represented at their source paths because their implementation was not excerpted; links are limited to documented relationships or SOURCE INDEX references.
Main entry points: trader.rs Trader · python/engine.rs Python control plane · src/engine.rs Backtest engine · adapters Venue adapters
Components 21
Strategy orchestration
- Python control plane
crates/backtest/src/python/engine.rs - Controller
crates/system/src/controller.rs - Trader
crates/system/src/trader.rs - Backtest engine
crates/backtest/src/engine.rs - Simulation config
crates/backtest/src/config.rs - Simulation modules
crates/backtest/src/modules/mod.rs
Market data
- Data engine
crates/data/src/engine/mod.rs - Data streaming
crates/data/src/engine/streaming.rs - DeFi data engine
crates/data/src/defi/engine.rs - Historical data
crates/backtest/src/config.rs
Trading runtime
- Live execution
crates/live/src/execution/manager.rs - Order management
crates/execution/src/order_manager/manager.rs - Portfolio
crates/portfolio/src/manager.rs - Risk engine
crates/risk/src/engine/mod.rs
Connectivity and state
- Venue adapters
crates/adapters - WebSocket transport
crates/network/src/websocket/client.rs - Cache
crates/common/src/cache/database.rs - Message bus
crates/common/src/msgbus/typed_router.rs - State persistence
crates/persistence/src/backend/session.rs
Other components
- System user
- Venues and providers
Connections 23
- System user → Python control plane: configures
README.md - Python control plane → Backtest engine: controls
crates/backtest/src/python/engine.rs - Python control plane → Controller: orchestrates
README.md - Controller → Trader: manages
crates/system/src/controller.rs - Trader → Controller: references
crates/system/src/trader.rs - Backtest engine → Simulation config: uses config
crates/backtest/src/engine.rs - Backtest engine → Simulation modules: dispatches
crates/backtest/src/engine.rs - Python control plane → Simulation config: builds config
crates/backtest/src/python/engine.rs - Python control plane → Simulation modules: registers
- Backtest engine → Historical data: replays
README.md - Data engine → Data streaming: uses
crates/data/src/engine/mod.rs - DeFi data engine → Data engine: integrates with
crates/data/src/defi/engine.rs - Venues and providers → Venue adapters: provides API
README.md - Venue adapters → Data engine: normalizes data
README.md - Venue adapters → Live execution: connects orders
README.md - Venue adapters → WebSocket transport: uses transport
- Trader → Live execution: runs live
README.md - Live execution → Order management: routes orders
- Order management → Portfolio: updates state
- Order management → Risk engine: checks orders
- Trader → Cache: uses shared state
README.md - Trader → Message bus: uses messaging
README.md - Trader → State persistence: persists state
README.md