MultiConnectMultiConnectDocs Website home
MultiConnectSDK › Developer Guide

6. Architecture

Combined Server (Single Server)

Best for small to medium games where one server handles everything.

┌─────────────┐                    ┌────────────────────┐
│   Client    │ ◄─────────────────►│  Combined Server   │
│   (Unity)   │ Reliable+Unreliable│  (Master + Game)   │
└─────────────┘                    └────────────────────┘

Distributed Architecture (Master + Game Servers)

Best for large-scale games requiring load balancing across multiple servers.

┌─────────────┐                    ┌────────────────────┐
│   Client    │ ◄─────────────────►│   Master Server    │
│   (Unity)   │    1. Connect      │  (Matchmaking &    │
└─────────────┘                    │   Load Balancer)   │
      │                            └────────────────────┘
      │                                     │
      │ 3. Connect to                       │ 2. Assigns best
      │    assigned server                  │    available server
      ▼                                     ▼
┌─────────────┐                    ┌────────────────────┐
│   Client    │ ◄─────────────────►│   Game Server 1    │
│   (Unity)   │    Game Traffic    │   (Game Logic)     │
└─────────────┘                    └────────────────────┘
                                   ┌────────────────────┐
                                   │   Game Server 2    │
                                   │   (Game Logic)     │
                                   └────────────────────┘
                                   ┌────────────────────┐
                                   │   Game Server N    │
                                   │   (Game Logic)     │
                                   └────────────────────┘

Flow:

  1. Client connects to Master Server
  2. Master Server performs matchmaking and assigns the best available Game Server
  3. Client connects to the assigned Game Server for gameplay