Skip to main content

System Requirements for IguanaX HA

Overview​

This document provides a high-level overview of the minimum system requirements needed to run IguanaX in a High Availability (HA) configuration. It is intended to help customers understand what hardware and infrastructure are typically required to get started with IguanaX HA.

A standard IguanaX HA deployment consists of:

  • Two IguanaX application servers

    • One Active

    • One Passive

  • A load balancer to route traffic and detect failures

  • (For shared-queue HA designs) Shared storage for logs and message queues

Both IguanaX servers must be sized to handle full production load independently, since either server may become Active during failover.

Minimum Hardware Requirements​

A. IguanaX Application Servers​

Component

Minimum Requirement

Quantity

2 identical servers

Operating System

Linux (preferred), Windows Server (subject to SMB performance validation)

CPU

Intel i3 or equivalent processor, or higher

Memory

2 GB min. 4 GB+ recommended 

Inter-Node Connectivity

Both servers must be able to communicate with each other for heartbeat and failover monitoring

For detailed IguanaX requirements, refer to the IguanaX System Requirements documentation.

B. Load Balancer (Customer-Provided)​

A load balancer is commonly used in IguanaX HA deployments and must be selected and managed by the customer.

Minimum capabilities (when used):

  • Virtual IP (VIP)

  • Health checks to IguanaX:

https://<host>:7654/os  → HTTP 200

  • Support for:

    • LLP / MLLP

    • HTTP / HTTPS

  • Automatic failover within a few seconds

A load balancer is optional if IguanaX is used only for polling components (for example, reading files or querying databases).

If no inbound LLP or HTTP traffic is required, a load balancer is not needed.

C. Shared Storage​

Shared storage is required for queue recovery and message sequencing IguanaX failover.

Component

Suggested Requirement

Type

Enterprise NAS or Cloud File Service

Protocol

NFS (preferred), SMB (subject to performance validation)

Capacity

≥ 500 GB usable

Access

Read/Write from both IguanaX servers

Performance

Low-latency, stable file locking

*Linux with NFS is strongly recommended for IguanaX HA.*

  • SMB-based storage can work but typically delivers lower performance for HA workloads.

  • SMB generally performs worse than NFS when handling a high volume of small files. While SMB3 is optimized for large file transfers in Windows environments, NFS has lower overhead and is better suited for frequent small file operations such as IguanaX logs and configuration updates.

  • When using SMB on Windows, additional configuration is required to ensure correct file ownership and sufficient privileges for IguanaX, since all configurations and logs reside on the shared SMB drive.

Sizing, Scoping, and Validation​

The system requirements listed in this document represent a typical minimum baseline for IguanaX High Availability. Actual requirements will vary depending on workload and usage patterns, and this page does not cover Disaster Recovery (DR), multi-cluster HA, or advanced Active-Active designs.

Before deploying IguanaX HA into production, customers are strongly encouraged to:

  • Review current production metrics

    • CPU utilization

    • Memory usage

    • Inbound and outbound throughput (TPS)

    • Daily log growth

  • Conduct a formal HA scoping exercise

  • Perform performance and failover testing on the target HA hardware

System sizing for IguanaX HA should always be based on measured production data, not estimates.

Getting Started​

This document provides only high-level guidance.

For help with:

  • HA scoping

  • Hardware sizing

  • Performance testing

  • Architecture validation

Please contact:

Our team can help ensure your IguanaX HA deployment meets your availability and performance requirements.