Architecture Overview

Architecture Overview

ServerFabric uses a split architecture.

Flow

ServerFabric-Client
→ plugin messages
→ ServerFabric-Proxy
→ HTTP
→ ServerFabric-Host

Responsibilities

ServerFabric-Host

Owns the actual resources:

• instance folders
• server jars
• processes
• build cache
• runtime stats

ServerFabric-Proxy

Acts as controller/router:

• knows configured hosts
• routes actions to the correct host
• registers instances into the proxy
• exposes SFabricAPI

ServerFabric-Client

Provides in-game administration:

• browse instances
• browse templates
• start/stop/restart/kill
• join servers
• view instance details and stats

SFabricAPI

Public integration layer for other proxy-side plugins.

Design goal

ServerFabric-Host is the resource owner.
ServerFabric-Proxy is the controller.
The proxy can restart without restarting the running instances.