For example, a middle tier provides not only another location for application processing but a mechanism to multiplex the database server as well. TP Monitors TP monitors sit between the client and a resource and can process transactions on behalf of one or many clients. A resource can be a queue or an API, but in most cases it is a database server. The basic idea is that a developer builds services within the TP monitor environment. TP monitors can reduce an application to a transaction level, breaking it down to many transactions or events that are bound together by a front end.
Developers create most application functions as transactions with a beginning, a middle, and an end.
These are usually granular functions such as updating a customer database with new customer information or deleting rows from several heterogeneous databases at the same time. This rollback means that network and database problems won t leave your system or data in an undesirable condition. TP monitors can also perform load balancing, which means that the TP monitor can move processing around to maximize available resources. TP monitors can also restart servers and report trouble to a central console. Of course, each TP monitor does these things in its own proprietary way.