Expandable database design -


I have a back-end system that needs to unite all games (Game 1, Game2, Game3, Etc.) is my initial design:

A centralized user DB (User ID and type of game is here), and each game keeps its own DB (from game type to user ID tagging here)

However, due to budget constraints this time DB has been chosen since hosting the server. Should. Can be extended in the future (meaning each game has its own user DB, however, user management will be another issue of duplication).

In order to expand the user management module, with any idea of ​​appropriate design, with minimal change?


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -