LogoLogo
English
English
  • Diarkis Help Center
  • Overview of Diarkis
  • Getting Started
    • Diarkis Server Template
    • Diarkis Client SDK
    • Tutorials
      • 1. Launch Diarkis Server in Local Environment
      • 2. Perform Connectivity Check with Test Client
      • 3. Implement Custom Command
      • Connect to Server from Diarkis Client
    • Samples
  • Diarkis Modules
    • Room Module
      • Set Up Room Module on Server
      • Room Sample
        • room_broadcast
      • Utilizing Room Module from Client
      • Additional Features of Room
    • MatchMaker Module
      • Set Up MatchMaker Module on Server
    • Field Module
      • Set Up Field Module on Server
    • P2P Module
      • Set Up P2P Module on Server
      • P2P Sample
    • DM (Direct Message) Module
      • Set Up DM Module on Server
    • Notifier Module
      • Set Up Notifier Module on Server
    • Session Module
      • Set Up Session Module on Server
    • Group Module
      • Set Up Group Module on Server
  • Diarkis Server
    • Launch Diarkis Server in Cloud Environment
      • AWS
    • Launch Diarkis Server on Windows Environment
    • MARS Server
    • UDP Server
    • TCP Server
    • HTTP Server
    • Metrics API
    • Inter-server Communication - Mesh
  • Diarkis Client
    • Runtime Library
      • Diarkis RUDP
    • Diarkis Module
      • Initialization and Termination of Diarkis Module
      • Customization of Diarkis Module
      • Logging System of Diarkis Module
      • Migration
      • Threads of Diarkis
    • Samples
      • C++
        • room_broadcast
        • directmessage_simple
        • group_sample
        • matching_and_turn
        • matchmaker_ticket
        • p2p_rudp_sample
        • session_simple
      • Unreal Engine Plugin
        • FieldWalker
      • Unity Plugin
        • FieldWalker
          • HowToReplicatePosition.md
  • Diarkis Tools
    • Diarkis CLI
      • Procedures to Switch to Diarkis CLI v3
  • References
    • API Reference
    • Release Notes
      • v1.0
      • v1.0.1
      • v1.0.2
      • v1.0.3
      • v1.0.4
      • v1.0.5
      • v1.0.6
  • Support
    • License and Billing
Powered by GitBook
On this page
  • Overview
  • Scalability in Diarkis Field
  • How Diarkis Field Works
  • Load Distribution and Dynamic Reallocation in Diarkis Field

Was this helpful?

  1. Diarkis Modules

Field Module

A cluster-wide, spatial awareness module that enables real-time proximity-based interaction and visibility across distributed clients, regardless of their connected server.

PreviousSet Up MatchMaker Module on ServerNextSet Up Field Module on Server

Last updated 1 month ago

Was this helpful?

Overview

Diarkis Field provides a shared, spatially-aware digital environment that spans the entire Diarkis server cluster, allowing users connected to different nodes to interact seamlessly within a unified virtual space. This module enables server-agnostic entity visibility and real-time proximity-based communication.

Core Functionality:

  • Cluster-Wide Spatial Awareness: Users connected to any Diarkis server node are registered within the Field as positioned entities. Clients transmit coordinate data (e.g., X, Y, Z) to the server, which performs cluster-wide visibility calculations to determine which users fall within each other’s defined visibility range.

  • Cross-Server Interaction: Unlike conventional systems where users must be connected to the same physical server to exchange packets, Diarkis Field enables inter-server interaction, eliminating boundaries between nodes. This allows all users in the Field to discover, interact with, and transmit data to nearby entities regardless of their server origin.

  • Dynamic Visibility and State Management: The Field module continuously tracks positional updates and dynamically adjusts visibility scopes, ensuring that only relevant updates and messages are transmitted between clients based on spatial proximity. This reduces unnecessary network load and improves scalability in large-scale environments.

  • Use Cases: Diarkis Field is ideal for implementing features such as:

    • Real-time entity tracking in open-world or simulation environments

    • Spatially-limited chat, interaction, or object syncing

    • Scalable multi-region digital twins or training simulations

For integration guidelines, configuration parameters, and advanced features such as filtering and custom visibility logic, refer to the .

Scalability in Diarkis Field

Diarkis Field is architected as a cluster-wide spatial system, with its state and visibility logic distributed across multiple nodes within the Diarkis server cluster. This design enables horizontal scalability, where performance and capacity can be dynamically adjusted by adding or removing servers from the cluster.

Each server in the cluster contributes to Field-wide processing, including position updates, visibility resolution, and packet routing, without central coordination or bottlenecks. As new servers are introduced, they automatically integrate into the cluster, distributing load and expanding capacity for handling more concurrent entities and larger spatial volumes.

This elastic scalability model allows Diarkis Field to efficiently support large-scale, real-time environments, such as massive multiplayer worlds, simulation spaces, or sensor fusion systems, with minimal operational overhead.

How Diarkis Field Works

Load Distribution and Dynamic Reallocation in Diarkis Field

As additional servers are introduced into the Diarkis server cluster, the overall user load is proportionally distributed, reducing the computational and network burden on individual nodes. Diarkis leverages a decentralized load-balancing mechanism that ensures efficient partitioning of user data and visibility calculations across all active servers.

When the cluster configuration changes—such as scaling in or out—the system automatically performs stateful reallocation of users to the appropriate servers. This reallocation is handled transparently and without service disruption, ensuring that real-time synchronization, visibility resolution, and packet exchange remain consistent throughout the transition.

This dynamic scaling capability enables elastic adaptation to fluctuating user volumes while preserving session continuity and ensuring high availability across distributed, spatially-aware applications.

Diarkis Field API documentation