System Architecture - Basic Cluster

System Architecture - Basic Cluster

For most production environments, the recommended deployment model is a clustered XPLG architecture, which provides improved scalability, resilience, and performance.

A cluster consists of multiple XPLG processes that can run either:

  • On a single machine (multi-process setup), or

  • Across multiple machines (distributed cluster)

XPLG’s clustering mechanism is fully automated, dynamically distributing tasks and workloads across available processes to ensure optimal system performance and resource utilization.


Key Advantages of a Clustered Deployment

  • Scalability
    Capacity can be increased incrementally by adding additional processes or nodes, enabling the system to support virtually any data volume (subject to infrastructure constraints such as network and storage).

  • Workload Separation
    The architecture enables a clear separation between user-facing activities (UI, queries, dashboards) and backend data processing, ensuring consistent performance and high quality of service.

  • High Availability
    All cluster nodes are capable of performing critical tasks such as data processing and alerting, eliminating single points of failure and maintaining service continuity.

  • Fault Tolerance
    In the event of a node or process failure, XPLG automatically redistributes workloads to remaining nodes, ensuring uninterrupted operation and continued data processing.

  • Disaster Recovery (DR)
    Built-in mechanisms continuously maintain configuration backups, allowing for fast and reliable system restoration when needed.


Single-Machine Cluster

The simplest clustered deployment model is a single-machine cluster, which runs multiple XPLG processes on the same host.

This setup is typically suited for:

  • Small to mid-sized environments

  • Initial production deployments requiring improved resilience over a single-process setup


Architecture Overview

The diagram below illustrates a clustered environment, highlighting the separation between user interface nodes and data processing nodes, as well as the distributed nature of data ingestion and processing across the cluster.

[0] Integration to Active Directory / SSO for authentication and authorization.

[1] UI Process - a process dedicated to serve users activity.

[2] Master/Processor process - the cluster orchestrator and processing engine.

[3] Storage - a file system based storage accessible by all cluster nodes.

[0] Integration to Active Directory / SSO for authentication and authorization.

[1] UI Process - a process dedicated to serve users activity.

[2] Master/Processor process - the cluster orchestrator and processing engine.

[3] Storage - a file system based storage accessible by all cluster nodes.


Getting Started

For detailed setup and configuration instructions, refer to the installation instructions
For architecture planning or deployment assistance, the XPLG support team is available support@xplg.com