Cross-Server

Cross-Server

Wonder supports three roles:

Role	What it does
LOCAL	Single-server mode. No Redis required.
ORCHESTRATOR	Participates in the queue and performs matching.
WORKER	Participates in the queue and claims, but does not perform matching.

Local Mode

For one server:

wonder {
  role = "LOCAL"
  redis {
    enabled = false
  }
}

This is the easiest way to run Wonder.

Redis Mode

For multi-server Wonder, enable Redis and set a unique server-id:

wonder {
  role = "ORCHESTRATOR"

  redis {
    enabled = true
    url = "redis://localhost:6379"
    server-id = "wonder-main"
    pool-size = 8
  }
}

Worker example:

wonder {
  role = "WORKER"

  redis {
    enabled = true
    url = "redis://localhost:6379"
    server-id = "wonder-worker-2"
    pool-size = 8
  }
}

Matching Responsibility

Only LOCAL and ORCHESTRATOR instances perform matching. WORKER nodes still:

• accept queue submissions
• show status/history/results
• allow claims and cancellations

But they do not attempt to create matches themselves.

Practical Topology

Typical setup:

• one orchestrator for matching authority
• one or more workers for player-facing entry points

That keeps matching centralized while still letting multiple servers feed the same Wonder queue.