DB Cache Server and Client

The DB cache of the ProudNet DB system is a subsystem for reading/writing the game database, and the database contents are cached in the server memory to reduce the load on the DBMS.

Other servers, such as game servers and authentication servers, must have a DB cache client, which connects to the DB cache server and accesses the game DBMS indirectly, usually through stored procedure.

ProudDB cache server and client configuration chart

DB Cache server

The DB cache server is the only process that has direct access to the game DBMS. This is because the latest contents of the DB cache may not yet be reflected in the game DBMS.

If you want to make changes elsewhere to the contents of the game DBMS that the DB cache is accessing, use non-proprietary data access.

DB cache client

The DB cache client loads object information from the game DBMS, and the DB cache client can read as much as it wants without overloading the DBMS. If the information loaded by the DB cache client is modified by a unilateral data change, the contents are sent to the DB cache server. When a DB cache system receives a modification request from a DB cache client, it does not immediately write to the DBMS, but instead updates the value in memory on the DB cache server. It writes to the DBMS when a certain time or milestone (defined by the server user) arrives.