transaction : Java Glossary

home page go to the Java Glossary Home go to the Computer Buyer’s Glossary up jump to foot of page Google search web for more information on this topic Pinterest pin button
* 0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (all)
©1996-2017 Roedy Green of Canadian Mind Products

transaction
A transaction is an atomic unit of work to be done to a database. It is always applied as a whole, If the database crashes and is recovered, only complete transactions will be reapplied, no partially completed ones. Often it is possible to abort a transaction part way through and the work done so far is undone. In a multithread situation, other threads don’t see the partially completed changes of some other transaction. Sometimes the term means a message sent over the Internet to a server. Sometimes it means a demarkated group of messages sent to a database.

Unless you have a very simple system, if you have networks of interconnected persistent objects that have to stay in sync, you pretty well have to use some sort of transaction management to cover all the myriad ways you could fail.

Without some sort of transaction manager, it requires expontially complicated code to back out of every possible failure. The code cannot be fully exercised during debugging and it will only fail at the JavaOne demo before the people from HP (Hewlett Packard) who are thinking of bundling your product with every computer they sell.

The three most common ways of doing transaction management are SQL, EJBand PODs.

This page is posted
on the web at:

 http://mindprod.com/jgloss/transaction.html

Optional Replicator mirror
of mindprod.com
on local hard disk J:

 J:\mindprod\jgloss\transaction.html
Canadian Mind Products
Please the feedback from other visitors, or your own feedback about the site.
Contact Roedy. Please feel free to link to this page without explicit permission.

IP:[65.110.21.43]
Your face IP:[3.138.34.93]
You are visitor number