Abstract
Transactions are fundamental to applications in order to ensure consistent behavior for data. In addition, they are a fundamental building block for ensuring the implementation of atomic, consistent, independent, and durable (ACID) behavior in an application. In the QuickReturns Ltd. application, ACID behavior means that when you do make a trade, it is absolute. It will either be complete in its entirety or be rolled back, leaving no room for ambiguity. If you were to put in a buy order for a stock, you would definitely want to be sure that the trade were absolute, right? Without transactions, you would not be sure that the trade was indeed conducted, and you would have no means of verifying the validity without ambiguity. Having a transactional system ensures that trades are consistently applied and are final. After all, you want to be clear about whether a trade has actually occurred.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2007 Chris Peiris and Dennis Mulder
About this chapter
Cite this chapter
(2007). Using Transactions in WCF. In: Pro WCF. Apress. https://doi.org/10.1007/978-1-4302-0324-7_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0324-7_9
Publisher Name: Apress
Print ISBN: 978-1-59059-702-6
Online ISBN: 978-1-4302-0324-7
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)