Skip to content

This is general knowledge or an external-engine reference, not an Apollo architecture or implementation claim. See Apollo's architecture status for target terminology and verified implementation boundaries.

Q1: Draw an MMORPG server architecture diagram you are familiar with, and explain the responsibilities of each component and how they communicate ​

Problem Analysis ​

This question tests your understanding of the overall MMORPG server architecture. You need to:

  1. Draw a complete server architecture diagram
  2. Explain the responsibilities of each component
  3. Explain how the components communicate with each other

Reference Architecture: BigWorld/KBEngine Style ​

Note: This answer uses the typical BigWorld/KBEngine process model, without mixing in a generic Gateway front-end architecture.

Overall Architecture Diagram ​

flowchart TB
    subgraph Clients["Client Layer"]
        U["Unity Client"]
        W["Web Client"]
        M["Mobile Client"]
    end

    subgraph Login["Login Service"]
        LA["LoginApp<br/>Login Server"]
    end

    subgraph Mgr["Management Service Layer"]
        BAM["BaseAppMgr<br/>BaseApp Manager"]
        CAM["CellAppMgr<br/>CellApp Manager"]
    end

    subgraph Base["Base Service Layer"]
        BA1["BaseApp1<br/>Proxy/Base Entity"]
        BA2["BaseApp2<br/>Proxy/Base Entity"]
        BA3["BaseApp3<br/>Proxy/Base Entity"]
    end

    subgraph Cell["Space Service Layer"]
        CA1["CellApp1"]
        CA2["CellApp2"]
        CA3["CellApp3"]
        CA4["CellApp4"]
    end

    subgraph Data["Data Service Layer"]
        DBM["DBMgr<br/>Database Manager"]
        RD["Redis<br/>Cache Cluster"]
        DB[("MySQL<br/>Database")]
    end

    subgraph Other["Other Services"]
        CHAT["ChatApp<br/>Optional Chat Service"]
        MATCH["MatchApp<br/>Optional Matchmaking Service"]
    end

    %% Connection relationships
    U & W & M --> LA
    U & W & M -.Reconnect after login.-> BA1
    U & W & M -.Reconnect after login.-> BA2
    U & W & M -.Reconnect after login.-> BA3

    LA --> BAM
    LA --> DBM

    BAM <--> BA1
    BAM <--> BA2
    BAM <--> BA3

    BA1 --> CA1
    BA1 --> CA2
    BA2 --> CA2
    BA2 --> CA3
    BA3 --> CA3
    BA3 --> CA4

    CAM <--> CA1
    CAM <--> CA2
    CAM <--> CA3
    CAM <--> CA4

    BA1 & BA2 & BA3 --> DBM

    BA1 & BA2 & BA3 --> RD

    DBM --> DB

    BA1 & BA2 & BA3 --> CHAT
    BA1 & BA2 & BA3 --> MATCH

    style LA fill:#e1f5ff
    style DBM fill:#fff4e1
    style BAM fill:#f0e1ff
    style CAM fill:#f0e1ff

Login Flow Diagram ​

sequenceDiagram
    participant C as Client
    participant LA as LoginApp
    participant DBM as DBMgr
    participant BAM as BaseAppMgr
    participant BA as BaseApp
    participant CA as CellApp

    C->>LA: Login request (account/password)
    LA->>DBM: Request account verification
    DBM-->>LA: Return verification result

    alt Login failed
        LA-->>C: Login failed
    else Login succeeded
        LA->>BAM: Request BaseApp assignment
        BAM-->>LA: Return BaseApp address
        LA->>BA: Create Base/Proxy
        BA->>DBM: Load player data
        DBM-->>BA: Return player data
        BA->>CA: Create Cell Entity
        LA-->>C: Return BaseApp address/token
        C->>BA: Disconnect from Login and reconnect to BaseApp
    end

Detailed Component Responsibilities ​

1. Client Layer ​

ComponentDescription
Unity ClientMainstream game engine for PC
Web ClientH5 mini-games, web games
Mobile ClientiOS/Android native or Unity export

2. Access Layer ​

LoginApp + BaseApp/Proxy (main access path) ​

Responsibilities:

  • LoginApp handles first access, account verification, and assigning the target BaseApp
  • The Proxy in BaseApp serves as the player's long-term session anchor
  • Handles client message encoding/decoding, session management, and disconnect/reconnect
  • Forwards messages that require spatial computation to CellApp

Communication:

  • With clients: usually TCP long connections + custom binary protocol/Protobuf
  • With internal services: inter-process TCP + internal messages/RPC

3. Login Service ​

LoginApp (Login Server) ​

Responsibilities:

  • Account/password verification
  • Coordinates with BaseAppMgr to assign the target BaseApp
  • Creates login tickets or connection information
  • Returns the address for subsequent access

Communication:

  • With DBMgr: RPC
  • With BaseAppMgr: RPC

4. Management Service Layer ​

BaseAppMgr (BaseApp Manager) ​

Responsibilities:

  • Manages all BaseApp instances
  • Handles new player connection assignment
  • BaseApp load balancing
  • Tracks BaseApp status

CellAppMgr (CellApp Manager) ​

Responsibilities:

  • Manages all CellApp instances
  • Space partitioning load balancing
  • Dynamically adjusts Cell boundaries
  • Entity cross-CellApp migration scheduling

5. Base Service Layer ​

BaseApp (Base Application) ​

Responsibilities:

  • Manages the player's Base / Proxy
  • Handles non-spatial logic:
    • Inventory system
    • Friend system
    • Mail system
    • Quest system
    • Mall transactions
  • Serves as the communication anchor for the client
  • Forwards space-related requests to CellApp
  • Responsible for player data loading, saving, and lifecycle management

Communication:

  • With clients: long connection
  • With CellApp: long-connection RPC
  • With DBMgr: asynchronous RPC

6. Space Service Layer ​

CellApp (Cell Application) ​

Responsibilities:

  • Manages space regions (Cells)
  • Handles spatial logic:
    • Player movement
    • AOI system
    • Combat system
    • NPC AI
    • Skill casting
    • Scene object management
  • Entity position management

Communication:

  • With BaseApp: long-connection RPC
  • With adjacent CellApps: Entity synchronization

7. Data Service Layer ​

DBMgr (Database Manager) ​

Responsibilities:

  • Database connection pool management
  • Asynchronous data access
  • Player data persistence
  • Account data management

Database partitioning:

  • AccountDB: account information, login records
  • CharacterDB: character data, attributes, inventory
  • WorldDB: world data, guilds, rankings

Redis (Cache Cluster) ​

Responsibilities:

  • Hot data caching (in practice usually accessed by services such as BaseApp)
  • Real-time leaderboard computation
  • Session/state auxiliary storage
  • Distributed coordination auxiliary capability

8. Other Services ​

ChatApp (Chat Service) ​

Responsibilities:

  • Channel chat (world, guild, team)
  • Private chat
  • System broadcast
  • Sensitive word filtering

MatchApp (Matchmaking Service) ​

Responsibilities:

  • Player matchmaking (PVP, instances)
  • Team formation
  • Matchmaking algorithms (ELO, rank tiers)

Communication Summary ​

Communication Protocol Stack ​

┌─────────────────────────────────────────────────────────────┐
│                      Business Protocol Layer                 │
│   Protobuf message definitions + RPC interface definitions  │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│                      Transport Protocol Layer                │
│   Client↔Login/Base: TCP long connection                    │
│   Internal services: TCP long connection                    │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│                      Network Layer                           │
│   IP + routing                                               │
└─────────────────────────────────────────────────────────────┘

Message Format ​

┌──────────────┬──────────────┬──────────────┬──────────────┐
│   PacketLen  │   MsgType    │   MsgID      │   Body       │
│   (4 bytes)  │   (2 bytes)  │   (4 bytes)  │   (Protobuf) │
└──────────────┴──────────────┴──────────────┴──────────────┘

RPC Call Flow ​

sequenceDiagram
    participant A as Service A
    participant B as Service B

    A->>B: RPC request (RequestID, Method, Params)
    B-->>A: RPC response (RequestID, Result/Error)

    Note over A,B: Asynchronous processing, supports concurrent requests

Architecture Characteristics Summary ​

CharacteristicDescription
Layered designClient → LoginApp/BaseApp → CellApp/data services, with clear responsibilities
Space separationBaseApp handles non-spatial logic, CellApp handles spatial logic
Horizontal scalingBaseApp/CellApp can be dynamically added or removed
High availability potentialCell/Base can scale horizontally, but LoginApp, Mgr, and DBMgr still need additional HA solutions
Asynchronous communicationInternal asynchronous RPC improves throughput

References ​

Released under the MIT License