Backend Architect Analysis
TRADARS 2.0 Backend Redesign & Mainframe Architecture
Mission
Goal 1: Re-engineer by Frontend
Analyze every frontend page to understand data needs, then build backend to serve it perfectly. App looks 100% identical, but backend is redesigned from scratch.
Goal 2: Central Mainframe Architecture
Price/Data APIs → Single Mainframe → All Frontend Consumers. One flow, no duplication, all features pull from same source of truth.
Goal 3: Zero Data Duplication
Eliminate redundant entities like IntradayPriceHistory, DailyPriceHistory, MarketPriceHistory all storing the same data. Single consolidated entity per data type.
Goal 4: Efficient Data Use
Compute metrics once (correlation, seasonality, risk), cache them, reuse everywhere. No more fresh computation per page load.
Current State Issues
200+ backend functions with scattered responsibilities
Overlap, redundancy, hard to maintain
Duplicate price entities causing 404 errors
IntradayPriceHistory has zero-volume duplicates, cleanup ineffective
Data sync failures and inconsistency
Economic data scattered across 3+ entities, Kajabi sync lags
Inefficient derived metric computation
Risk scores, correlations, seasonality computed fresh per page load
Next Steps
1. Review this architecture design with your team
2. Answer critical questions: latency tolerance, concurrency, revenue-critical features
3. Prioritize Phase 1 (blueprint) - audit all pages and functions
4. Begin mainframe entity creation alongside existing system
5. Migrate APIs one-by-one to minimize risk