Java theory and practice, Understanding JTS -- Balancing safety and performance

Guidelines for transaction demarcation and isolation

From the developerWorks archives

Brian Goetz

Date archived: February 27, 2017 | First published: May 01, 2002

In Parts 1 and 2 of his series on JTS, Brian covered the basics of what transactions are and how J2EE containers make transaction services transparent to EJB components. While being able to specify a component's transactional semantics declaratively instead of programmatically offers a great deal of flexibility in configuring enterprise applications, making poor decisions at application assembly time can impair the performance and stability of your applications. In this final installment, Brian looks at the facilities that J2EE offers for managing transaction demarcation and isolation and some guidelines for using them effectively.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

Zone=Java development
ArticleTitle=Java theory and practice: Understanding JTS -- Balancing safety and performance