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
Wednesday, July 27, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- Java Examples - JExamples.com
- as400 iSeries NetServer Disabled user profiles
- Create a Custom Live Linux CD - Leveraging BusyBox and OpenSSH
- Search for text in vi or vim
- IBM eServer iSeries - iSeries NetServer: Command Line Setup
- Super $500 Myth Project
- Encode HTML Entities - Showing code in blogs
- HOW TO make a Powerbook in to a Wi-Fi access point!
- iReport - OpenSource Java Reporting Tool
- Reno County is preparing to move from an AS400 computer system to a personal-computer-based system
No comments:
Post a Comment