4. System Architecture

• 4.1. Database Technology Assessment
  • 4.1.1. TL;DR
  • 4.1.2. Executive Summary
  • 4.1.3. Data Volume Projection
    • 4.1.3.1. Source Data Estimates
    • 4.1.3.2. WHG Attestation Layer
    • 4.1.3.3. AUTHORITY Collection (Shared)
    • 4.1.3.4. Total Raw Data
    • 4.1.3.5. Database-Specific Storage Characteristics
    • 4.1.3.6. Growth Projections
    • 4.1.3.7. Memory Requirements
    • 4.1.3.8. Storage I/O Requirements
  • 4.1.4. Option 1: ArangoDB
    • 4.1.4.1. Technical Advantages
    • 4.1.4.2. Deployment Considerations
    • 4.1.4.3. Limitations
    • 4.1.4.4. Assessment for WHG
  • 4.1.5. Option 2: PostgreSQL + Extensions
    • 4.1.5.1. Architecture
    • 4.1.5.2. Advantages
    • 4.1.5.3. Deployment Considerations
    • 4.1.5.4. Limitations
    • 4.1.5.5. Assessment for WHG
  • 4.1.6. Option 3: Neo4j
    • 4.1.6.1. Advantages
    • 4.1.6.2. Limitations
    • 4.1.6.3. Assessment for WHG
  • 4.1.7. Option 4: Vespa
    • 4.1.7.1. Why Vespa Was Initially Attractive
    • 4.1.7.2. Why the Data Model Redesign Changed Everything
    • 4.1.7.3. Critical Limitation 1: Not a Graph Database
    • 4.1.7.4. Critical Limitation 2: No GeoJSON Support
    • 4.1.7.5. Critical Limitation 3: Document Model vs. Attestation Model
    • 4.1.7.6. Critical Limitation 4: Query Pattern Mismatch
    • 4.1.7.7. What Vespa Does Exceptionally Well (But We Don’t Need)
    • 4.1.7.8. The Bottom Line
    • 4.1.7.9. Why Not Use Vespa for Vectors + Another DB for Graph?
    • 4.1.7.10. Assessment
  • 4.1.8. Detailed Comparison Matrix
  • 4.1.9. Recommendation
    • 4.1.9.1. Primary Option: ArangoDB
    • 4.1.9.2. Alternative: PostgreSQL + Extensions
  • 4.1.10. Next Steps
  • 4.1.11. Conclusion
• 4.2. Kubernetes Configuration
  • 4.2.1. Overview
    • 4.2.1.1. System Components
    • 4.2.1.2. Application Components
    • 4.2.1.3. Monitoring and Analytics Components
  • 4.2.2. Setup
    • 4.2.2.1. Prepare the Server Environment
    • 4.2.2.2. Deploy the Application
• 4.3. SSH Key Setup
  • 4.3.1. 1. Generate an SSH Key
  • 4.3.2. 2. Copy the Public Key to the Remote Server
  • 4.3.3. 3. Log in to the Remote Server
  • 4.3.4. 4. Automatically Switch to the gazetteer Account
  • 4.3.5. 5. Check Kubernetes Nodes
  • 4.3.6. Secrets Management
• 4.4. Deploying the Management Pod
  • 4.4.1. Accessing Kubernetes Dashboard and Services Locally
• 4.5. Deploying Services
• 4.6. Service Configuration
  • 4.6.1. Proposed Subdomain Mapping