If you develop challenging distributed enterprise applications and systems, short ACID transactions are your friends. The ACID properties of transactions enable you to write software without considering the complex environment in which the application runs. ACID transactions bring simple high-school programming to the complex real world. With ACID transactions you can concentrate on the application logic and not on failure detection, recovery and synchronizing access to shared data.
With ACID transactions, your software need not include logic to recover the state of the application should it fail. Instead you simply define transaction boundaries in your application and the system ensures atomicity the actions taken within the transaction will happen completely, or not at all. If the application fails midstream, the system will recover to the previous state, as if the transaction never took place. If you have ever written an application without transactions that attempted to detect failures and recover from them, you know that logic can get quite complex
- Javalobby - Java J2EE Programming Forums - Coldtags suite 2.1: 210+ custom JSP tags
- SOA: Refactoring Mainframe Applications into Dynamic Web Applications (Part 1)
- as400 Iseries Tips
- Journaling for Performance
- What is QZHQSSRV job?
- Free Iseries Accounts Available
- AS400 APIs
- Wordpress games Google by hosting LinkFarm
- ibm as400 manuals v5r4
- Trying to find out as400 library size