// writing
Engineering notes from the framework.
Implementation walk-throughs, design rationale, and honest accounting of what dgbit is and is not. No "ten strategies that print money" content.
-
Why dgbit uses an NNG service bus, not HTTP between workers
The dgbit data, backtest, and strategy services talk to each other over an NNG IPC message bus rather than HTTP. This post explains the trade-offs that decision encodes and what it means for operators running the stack.
architectureinfrastructure -
How to wire a custom strategy module in dgbit
A walk-through of the BaseStrategy / StrategyMetadata / strategy_registry pattern from the dgbit README — what each piece is for, why the framework picks it over a DSL, and what you have to do to ship a strategy from notebook to live.
strategydeveloper-guide -
Why Bybit-specific matters for backtesting fidelity
Multi-exchange backtesting frameworks promise breadth and deliver vagueness. We make the case for binding the data fetcher, fee model, and execution layer to a single exchange — and why dgbit does so to Bybit.
backtestingdesign