How austin-starks/nexttrade works
Project type and purpose
• NextTrade is a full‑stack, monolithic trading platform.
• Frontend: React/TypeScript single‑page application for building and visualizing strategies, conditions, portfolios, backtests, optimizations, and live deployments.
• Backend: Node.js/TypeScript Express server exposing a REST API, implementing trading workflows (backtest, forward‑test, optimize, deploy) and persisting data in MongoDB.
• External integrations: Brokerage APIs (Tradier, Alpaca, Coinbase, etc.) for live deployments and data sourcing.
File structure
• Top‑level “client” and “app” directories separate frontend and backend.
• “client/src/pages” and “client/src/components” organize the UI into feature pages (Assets, Backtests, Optimization, Portfolios, Strategies, Authentication) and reusable components.
• “client/src/services/requests.tsx” encapsulates HTTP calls to the backend.
• “app/src/routes” → Express route definitions.
• “app/src/controller” → Controllers for each domain (backtestController, forwardtestController, optimizationController, portfolioController, etc.).
• “app/src/models” → Domain models and abstractions (Assets, Conditions, Strategies, Portfolios, History, Brokerage adapters, etc.)
• “app/src/services/db.ts” → MongoDB connection.
• “app/src/controller/*/worker.ts” → Background workers for long‑running tasks (backtest, forward‑test, optimize).
• Configuration files: tsconfig.json, nodemon.json, PM2 startup scripts (static.json).
README for insights
• Backend uses MongoDB for persistence, Jest for testing, PM2 for process management.
• Supports historical backtesting, genetic‑algorithm optimization, real‑time live trading via brokerage APIs.
• The platform is deployed via two processes: client and server.
Detail
• Break the Backend into: HTTP Server → Route Handlers → Controllers → Model Layer → DB.
• Worker processes separately, indicating they read from and write to the same DB.
• Process Manager (PM2) overseeing both client and server processes.