# Deployment and Operation

# Purpose of this Manual

This operations manual serves as a comprehensive guide for technical staff responsible for the installation, configuration, operation, and maintenance of the Nekuti Matching Engine. It provides detailed instructions and best practices to ensure optimal performance, security, and reliability of the system.

# Intended Audience

This manual is intended for:

• System administrators
• DevOps engineers
• Site reliability engineers
• Exchange operators
• Technical support staff

Readers are expected to have a strong background in server administration, database management, and general trading system operations.

# System Requirements

# Dedicated Server Deployment

• Hardware:
  • High-performance x86 servers with fast CPUs
  • At least 64GB RAM
  • Low-latency storage (local NVMe SSDs strongly recommended)
• Network:
  • Low-latency, high-bandwidth network connections between components (2.5-10 Gbps recommended)
• Operating System:
  • Linux (specific distribution requirements to be detailed in the Installation section)
• Additional Software:
  • Azul Java Runtime Environment 25 or later
  • Node.js
  • PM2 for process orchestration (optional)

# Cloud-Based Deployment

• Compute Resources:
  • High-performance virtual machines or dedicated instances
  • Equivalent to x86 servers with fast CPUs
  • Minimum 64GB RAM per instance
• Storage:
  • High-performance block storage (e.g., AWS EBS io2, Google Cloud SSD Persistent Disk)
  • Consider using local SSDs for even lower latency where available
• Networking:
  • Low-latency, high-bandwidth network connections between components
  • Use of placement groups or similar features to ensure co-location of related instances
  • Consider dedicated interconnects for hybrid cloud setups
• Operating System:
  • Linux-based cloud images (specific requirements to be detailed in the Installation section)
• Additional Services:
  • Load balancers for distributing traffic to User Gateways
  • Virtual Private Cloud (VPC) for network isolation
  • Identity and Access Management (IAM) for secure access control
• Software Requirements:
  • Same as non-cloud deployment:
    • Azul Java Runtime Environment 25 or later
    • Node.js
    • PM2 for process orchestration (optional)

This distributed architecture allows for horizontal scaling of user-facing components while maintaining a centralized, deterministic core for order matching and trade execution. The separation of concerns between different processes enhances security, reliability, and maintainability of the overall system.