Project Phoenix
TRADARS 2.0 Backend Redesign - Complete Architecture Specification
High-Level System Architecture
✓ Rate limiting ✓ Retry logic ✓ Error handling ✓ Credentials secure
• Data Validation (Integrity checks)
• Schema Transformation (Normalize to Mainframe)
• Deduplication (Upsert by unique key)
• Error Flagging (Invalid data → ErrorLog)
All canonical data:
All read FROM Mainframe, write results BACK to Mainframe
REST endpoints serving current frontend
Data only from Mainframe (no direct API calls)
Authentication/Authorization enforced
✓ No changes to user experience
Key Architecture Principles
Critical Issues Being Resolved by Project Phoenix
Kajabi Integration - User Lookup Failures
✓ Resolution: Dedicated Kajabi Client + proper User Mainframe sync ensures all active users found
Risk Radar COT 404 Errors
✓ Resolution: Dedicated CFTC Client with proper error handling, all COT data pre-synced to Mainframe
Zero-Volume IntradayPriceHistory Duplicates
✓ Resolution: Price Validator prevents bad data entry + Data Cleansing Job removes existing bad records
Missing Radar Operation Logging
✓ Resolution: All Radars instrumented with detailed SystemLog entries for every run
QuantAnalysisCache Inconsistency
✓ Resolution: Cache Manager maintains cache integrity after every analysis run