XHSC Clustering System

The XyPriss Hyper-System Core (XHSC) introduces a modern, high-performance approach to process management. Unlike traditional Node.js clustering, XyPriss utilizes a dedicated XHSC Master Coreto handle networking, load balancing, and worker lifecycle management.

Core Components

The architecture is split between a native high-speed master engine and standardized worker processes.

Native Load Balancing

Clustering Architecture

InternetClient Traffic
XHSC MasterLoad Balancer & Filter
Worker 1Node.js / Bun
Worker NNode.js / Bun
Isolation

Workers run in separate memory spaces.

Performance

Binary IPC over Unix Domain Sockets.

XHSC Master

A native Go-based process that manages network listeners, filters incoming requests, and distributes traffic with sub-millisecond overhead.

Worker Nodes

Node.js or Bun processes that receive pre-filtered requests via high-speed IPC, focusing purely on application logic execution.

Performance Advantages

Concurrency

XHSC efficiently manages thousands of persistent connections, offloading the network stack from the JS event loop.

Stability

Worker crashes are isolated. XHSC automatically detects failures and recycles processes without dropping active master connections.

Security Policy

Security is baked into the clustering logic, ensuring data isolation and resource protection.

  • Process Isolation: Each worker operates in its own memory heap, preventing cross-request memory leaks.
  • Native Guardrails: CPU and memory limits are enforced at the native level. Workers are gracefully recycled if thresholds are exceeded.
Legacy Note
Documentation referring to cluster.config is legacy. XHSC uses the flat configuration structure described in the following guides.
Cluster Configuration

Learn how to configure workers, distribution strategies, and resource limits.