Files
AI-Trader/docs/deployment/scaling.md
Bill b3debc125f docs: restructure documentation for improved clarity and navigation
Reorganize documentation into user-focused, developer-focused, and deployment-focused sections.

**New structure:**
- Root: README.md (streamlined), QUICK_START.md, API_REFERENCE.md
- docs/user-guide/: configuration, API usage, integrations, troubleshooting
- docs/developer/: contributing, development setup, testing, architecture
- docs/deployment/: Docker deployment, production checklist, monitoring
- docs/reference/: environment variables, MCP tools, data formats

**Changes:**
- Streamline README.md from 831 to 469 lines
- Create QUICK_START.md for 5-minute onboarding
- Create API_REFERENCE.md as single source of truth for API
- Remove 9 outdated specification docs (v0.2.0 API design)
- Remove DOCKER_API.md (content consolidated into new structure)
- Remove docs/plans/ directory with old design documents
- Update CLAUDE.md with documentation structure guide
- Remove orchestration-specific references

**Benefits:**
- Clear entry points for different audiences
- No content duplication
- Better discoverability through logical hierarchy
- All content reflects current v0.3.0 API
2025-11-01 10:40:57 -04:00

796 B

Scaling

Running multiple instances and load balancing.


Current Limitations

  • Maximum 1 concurrent job per instance
  • No built-in load balancing
  • Single SQLite database per instance

Multi-Instance Deployment

For parallel simulations, deploy multiple instances:

# docker-compose.yml
services:
  ai-trader-1:
    image: ghcr.io/xe138/ai-trader:latest
    ports:
      - "8081:8080"
    volumes:
      - ./data1:/app/data

  ai-trader-2:
    image: ghcr.io/xe138/ai-trader:latest
    ports:
      - "8082:8080"
    volumes:
      - ./data2:/app/data

Note: Each instance needs separate database and data volumes.


Load Balancing (Future)

Planned for v0.4.0:

  • Shared PostgreSQL database
  • Job queue with multiple workers
  • Horizontal scaling support