Look, I am not trying to diminish what you are doing, this is not a dong measuring contest. I am sure your services have value to people who are paying you and even a simple database can be used to extract craploads of interesting insights. "Complex" does not mean "more valuable", after all. However, what you have shown is a rather simple relational schema for, what I can assume, is an HR department, or something similar.
Anyway, this is not what we are talking about when we discuss CI, at least looking at what they have been claiming. We are talking about several layers of software, a self-authored, distributed system communicating over unreliable network, with a graph database at the core and message queues transferring information about requested transactions between game servers and the core DB.
This is not what would be sensible to replicate 1:1 on a single machine, in particular when there is no reason. Just like nobody sane would use a fully blown DB for storing local application state. They would go for an in-process solution like, idk, SQLite. Or just dump the state to a save file directly, since there is no issue if a single player game "pauses" for some time while it is saving. You can test it in plenty of games with on-demand quick-save. Spam it and the game starts stuttering.
Last edited: