Is like this, there is a design requirements:

Database needs multi-threaded concurrent read and write, and read and write the SQL statements are dynamic, the model can draw lessons from many producers - many consumers to carry on the design? Or if there is a warrior can be under the guidance, have what good design patterns? Pooling of database should have nothing to do with this?
Note:
Language is c + +, database SQLITE, or lightweight requires no additional deployment server database,

For a great god,

CodePudding user response:

Inside the database has been complicated by the optimization of reading and writing, users don't need to care about