I've been working on a distributed mmo cluster system, in which different business logic handle is distributed to different server.
In this system, I have a character server and a guild server. Character server owns all characters' base info, guild server owns all guilds' base info and all guild members' base info.
Both the character server and the guild server own character's level. When the character server updates a character's level, it first commits an update transaction to the database asynchronously. After the commit returns, the character server will publish a character-level-update message, the guild server will then subscribe the message and update the corresponding guild member's level.
My problem is, if the character server commits the update transaction, but crashes before the commit returns or before it publishes the character-level-update message, and then we restart the character server, characte level in the character sever will be the newest value, but guild member level in the guild server will still be the old value. Can anyone give any suggestion to solve this problem? Or is there anything wrong in my design? Thanks!
Here below is my cluster design:
Edited by iwitggwg, 28 August 2014 - 09:00 PM.