Editing Isolation (database systems) (section)

==Client-side isolation==
Isolation is typically enforced at the database level. However, various client-side systems can also be used. It can be controlled in application frameworks or runtime containers such as [[J2EE]] [[Entity Bean]]s<ref name="Stony Brook"/> On older systems, it may be implemented systemically (by the application developers), for example through the use of temporary tables.{{Failed verification|date=March 2024|reason=The paragraph source does not mention temporary tables.}} In two-tier, three-tier, or [[Multitier architecture|n-tier]] web applications a [[transaction manager]] can be used to maintain isolation. A transaction manager is [[Middleware (distributed applications)|middleware]] which sits between an app service (back-end application service) and the [[operating system]]. A transaction manager can provide global isolation and atomicity. It tracks when new servers join a transaction and coordinates an [[atomic commit]] protocol among the servers. The details are abstracted from the app, making transactions simpler and easier to code. A [[Transaction processing system|transaction processing monitor]] (TPM) is a collection of middle-ware including a transaction manager. A TPM might provide local isolation to an app with a lock manager.<ref name="Stony Brook">"The Architecture of Transaction Processing Systems", Chapter 23, Evolution of Processing Systems, Department of Computer Science, Stony Brook University, retrieved 20 March 2014, http://www.cs.sunysb.edu/~liu/cse315/23.pdf</ref>