Database and the Transaction Pool

A Common Database and Transaction Pool to Reduce Data Redundancy and to Maximize Database Throughput in an Integrated Software System of a Particular Domain

Main objective of writing this paper is to adopt and create a common database from multiple databases in an Integrated Software System of a particular domain of interest. This will result in reducing data redundancy, in reducing database maintenance time, in simplifying the development phase of the front-end interface, in minimizing the size of the system, in maximizing the database throughput and in implementing of a transaction pool. The transaction pool is used to optimize the database processing. The system can pool the database transactions. Transaction pooling maximizes database throughput while controlling the number of database connections that can be open at one time. We can also say the transaction pool will reduce the number of times new connection objects are created, will promote connection object reuse, will quicken the process of getting a connection and will control the amount of resources spent on maintaining connections. We also illustrate some examples of a transaction pool to connect transaction databases with a common database. We have also illustrated how to create non-visual transaction objects within the system. Practically, we have implemented this approach in our one integrated software system.