using-nautilus-trader

NautilusTrader strategy development involves defining indicators, orders via order_factory, and risk checks through RiskEngine. Start by preregistering indicators before subscribing to data, then structure your logic around the event-driven architecture to ensure consistency between backtesting and live execution.

Both backtesting and live trading use the same event-driven architecture and core components in NautilusTrader, enabling parity between environments. The Skill covers deployment patterns, adapter integration, and configuration differences so your strategy behaves identically in both runtimes.

NautilusTrader enforces risk management through RiskEngine, which validates orders before execution. The Skill guides you through configuring risk checks that apply consistently across backtesting and live trading to prevent unsafe positions.

Yes, NautilusTrader supports adapter integration across backtest and live runtimes. The Skill provides architecture references and integration points so you can connect data sources, execution venues, and other external services to your trading system.

Yes, NautilusTrader requires preregistering indicators before subscribing to data streams. This is a functional requirement enforced by the framework to maintain data flow integrity and ensure indicators receive the correct market data.

NautilusTrader provides market, limit, and stop orders through the order_factory, a required pattern for order creation. The Skill explains how to construct and submit each order type within the event-driven architecture.