DB cache client and server

DB cache system of ProudNet Database Cache System version 2 is a sub system that read and writes game database. And since the information in database gets cached in server memory, it can significantly reduce overload of DBMS.

DB cache system is structured in client and server. DB cache server is the only process that can directly access DBMS. Servers like game server and authentication server must have DB cache client. DB cache client connects to DB cache server and indirectly access game DBMS through stored procedure.

db_cache_server_client.jpg
Structure of ProudDB Cache Server and Client

DB Cache Server

DB cache server is the only process that can directly access DBMS. The main reason only DB cache server can access DBMS is possibly new information of DB cache has not applied to DBMS yet. So if you want to change information of DBMS that accessing by DB cache, we recommend using Accessing non-exclusive data.

DB Cache Client

DB cache client loads game DBMS’s information of objects. And such information can be read without giving any load to DBMS.

If any edit is made on the information loaded by DB cache client, the edited information gets passed to DB cache server. DB cache system doesn't immediately reflect corrections even though it receives the correction request from DB cache client. Instead, it refreshes values in memory of DB cache server. And finally when it reaches a specific or important time (defined by user), it starts writing in DBMS.