Problem description: there are about A - F database, demand: A new project data from current A - F A library, there are also new data from the project itself, the new project database A data modification, and then to synchronize to A library itself, and A library data modification, and synchronized to the new project, everything else is reading, so demand, how to architecture, database diagram are two ideas, request A great god better help, more about concurrent, pressure, speaking, reading and writing, data latency issue

CodePudding user response: