Translation: In the preliminary phase of our work, we have established the communication protocol and data structure of the project, and selected TCP protocol with JSON format for data transmission and parsing.

Entering the architecture design stage, we faced key decisions regarding the choice of thread model: whether to use multi-threading, multi-threading combined with coroutines, or single-threaded mode?

Given that database operations constitute a significant portion of I/O operations, primarily focusing on user registration, login, and player data archiving, among others. Specifically, the data archiving part can be handled entirely by an independent thread.

Therefore, we designed a dual-thread structure to handle a large volume of work: one main thread for game logic and another dedicated to database-related operations.

Benefiting from the network library encapsulated by YLIB, which is based on HPSocket, it supports high-concurrency connection management, thus reducing concerns about network communication. The network thread is responsible for receiving data, which is then directly passed to the main thread for processing after preliminary validation. If there are data update (UPDATE) operations in the main thread that consume a considerable amount of time, they are forwarded to the database thread for asynchronous processing.

Through this division of labor, we ensure both the coherence and real-time response of game logic, avoid blocking the main thread due to database I/O operations, and fully utilize the advantages of multi-core CPUs to improve the efficiency and stability of the entire game server.

Architecture design

Manager or contriller(unique instance)

Analysis Services

The service inherits the IService interface class and is bound and added to the ServiceManager during construction

Operation process