How venkatasaieeshreddy005/stocks_trading_platform works
TradeZen is a paper-trading application: users create or verify an account, explore live market data, place simulated orders, and review holdings, performance, and alerts. The client’s routed pages and shared auth/socket contexts form the user-facing workflow; backend routes dispatch requests to controllers, while the simulation engine maintains market state and processes market activity. Persistent user, order, holding, and alert models support account and trading state. The excerpts establish key route, model, simulation, and socket links; unsampled page and controller internals are not assumed.
Main entry points: simulation.js Price Simulation · App.jsx Application Routes · server.js HTTP and Socket Server · tradeController.js Trade Controller
Components 24
Trading Client
- Application Routes
client/src/App.jsx - Auth Context
client/src/context/AuthContext.jsx - Live Data Context
client/src/context/SocketContext.jsx - Dashboard
client/src/pages/Dashboard.jsx - Markets
client/src/pages/Markets.jsx - Instrument Detail
client/src/pages/InstrumentDetail.jsx - Portfolio View
client/src/pages/Portfolio.jsx - Orders View
client/src/pages/Orders.jsx - Watchlist View
client/src/pages/Watchlist.jsx
API and Accounts
- HTTP and Socket Server
backend/server.js - Auth Routes
backend/routes/auth.js - Account Controller
backend/controllers/authController.js - Session Middleware
backend/middleware/auth.js
Market Simulation
- Market Controller
backend/controllers/marketController.js - Price Simulation
backend/engine/simulation.js - Instrument Catalog
backend/data/instruments.js
Trading and Portfolio
- Trade Controller
backend/controllers/tradeController.js - Portfolio Controller
backend/controllers/portfolioController.js - Watchlist Controller
backend/controllers/watchlistController.js
Persistent State
- User Records
backend/models/User.js - Order Records
backend/models/Order.js - Holding Records
backend/models/Holding.js - Alert Records
backend/models/Alert.js
Other components
- Trader
Connections 38
- Trader → Application Routes: uses
client/src/App.jsx - Application Routes → Auth Context: provides
client/src/App.jsx - Application Routes → Dashboard: routes to
client/src/App.jsx - Application Routes → Markets: routes to
client/src/App.jsx - Application Routes → Instrument Detail: routes to
client/src/App.jsx - Application Routes → Portfolio View: routes to
client/src/App.jsx - Application Routes → Orders View: routes to
client/src/App.jsx - Application Routes → Watchlist View: routes to
client/src/App.jsx - Auth Context → Auth Routes: calls auth API
client/src/context/AuthContext.jsx - HTTP and Socket Server → Auth Routes: mounts
backend/server.js - Auth Routes → Account Controller: dispatches
backend/routes/auth.js - Auth Routes → Session Middleware: checks session
backend/routes/auth.js - Account Controller → Session Middleware: signs sessions
backend/controllers/authController.js - Account Controller → User Records: reads and writes
backend/controllers/authController.js - HTTP and Socket Server → Market Controller: mounts market routes
backend/server.js - Market Controller → Price Simulation: reads market state
backend/controllers/marketController.js - Price Simulation → Instrument Catalog: initializes from
backend/engine/simulation.js - HTTP and Socket Server → Price Simulation: starts and broadcasts
backend/server.js - HTTP and Socket Server → Live Data Context: streams market events
backend/server.js - Trader → Live Data Context: receives live updates
client/src/context/SocketContext.jsx - HTTP and Socket Server → Trade Controller: mounts trade routes
backend/server.js - Trade Controller → Price Simulation: gets prices; records trades
backend/controllers/tradeController.js - Trade Controller → User Records: updates balance
backend/controllers/tradeController.js - Trade Controller → Order Records: creates and updates
backend/controllers/tradeController.js - Trade Controller → Holding Records: updates positions
backend/controllers/tradeController.js - HTTP and Socket Server → Portfolio Controller: mounts portfolio routes
backend/server.js - Portfolio Controller → User Records: reads metrics and cash
backend/controllers/portfolioController.js - Portfolio Controller → Holding Records: reads positions
backend/controllers/portfolioController.js - Portfolio Controller → Order Records: reads executed sales
backend/controllers/portfolioController.js - Portfolio Controller → Price Simulation: gets instrument prices
backend/controllers/portfolioController.js - HTTP and Socket Server → Watchlist Controller: mounts watchlist routes
backend/server.js - Watchlist Controller → User Records: reads and updates list
backend/controllers/watchlistController.js - Watchlist Controller → Alert Records: uses alert records
backend/controllers/watchlistController.js - Watchlist Controller → Price Simulation: reads market state
backend/controllers/watchlistController.js - Price Simulation → Order Records: processes pending orders
backend/engine/simulation.js - Price Simulation → Holding Records: triggers stop losses
backend/engine/simulation.js - Price Simulation → User Records: updates trade state
backend/engine/simulation.js - Price Simulation → Alert Records: persists alerts
backend/engine/simulation.js