Principles of Transaction Processing, Second Edition (The Morgan Kaufmann Series in Data... at Dominant Systems Book Store

What do reserving a seat on an airplane, buying a movie ticket over the Internet, and launching a missile all have in common? Principles of Transaction Processing for the Systems Professional explains that these and many other computerized tasks require the use of transaction processing (TP). Authors Philip Bernstein and Eric Newcomer demonstrate that this previously specialized area of systems design is becoming more important with the growth of Internet commerce. This theoretically astute and practical-minded book begins with a description of the principles of successful transaction management. (The so-called "ACID" test requires that transactions be atomistic, consistent, isolated, and durable.) The authors illustrate the principles with real-world examples of transactions in everyday life, such as ATM systems and the stock market. Bernstein and Newcomer then outline how transaction processing monitors work and discuss some of the details, such as interface definition languages, which let disparate computers communicate, and remote procedure calls.

The text also explores some real-world TP monitor products, from IBM's CICS to Tuxedo to Microsoft Transaction Server. While transaction processing has been a part of mainframe system design for decades, it has recently become relevant for commerce and everyday database access on the Web. The authors look at today's Web servers--Microsoft Internet Information Server and Netscape's FastTrack Server--and show how they manage transactions. Additional chapters move back into the theoretical, with descriptions of database transactions and strategies for replicating data. The text finishes up with some predictions on where this vital and established technology is headed. This book is a must for any developer who is designing a Web site that connects users to data in a distributed environment. It's also a definitive guide to an intriguing area of computing. --This text refers to an out of print or unavailable edition of this title.

Customer Reviews & Comments
This book was written in 1997 which is often considered ancient in "Internet-years" but it is still very relevant because it focuses on fundamental principles of transaction processing (TP) rather than the latest whiz-bang technologies that optimize TP. For those of you who aren't TP experts, a transaction is a computer operation that meets the ACID test. ACID here stands for: Atomic - the steps that comprise transaction succeed or fail as one, there is no partial success. Consistent - the internal data structures of the system(s) remain consistent with business rules. Isolated - the data read or manipulated by the transaction is not altered during the duration of the transaction's execution. Durable - the results of the transaction are persisted Why does this matter to the system user or stakeholder? The canonical example is that of the ATM machine (or the "handy bank" if you're Australian). When you withdrawl money from an ATM, it has to go out and validate you have enough funds to meet the withdrawl, reserve those funds, and dispense cash - all within the same transaction. If the ATM failed after your bank account had been debited but before you'd gotten your money, you'd be very upset; conversely if the cash was dispensed but the debit procedure failed, the bank would be very upset. Ted provides very amusing analogy for this using a wedding ceremony but you can read that in his book. There's a whole lot more to transaction processing beyond ACID and the ATM example, including two-phase commit (TPC), high-availability, massive concurrency, and crash recovery. To find out about all of these topics, read the book. One thing to remember though is that most application developers will never have to deal with the extremely complex details of providing a working and robust transaction management implementation, but like any technology it's important to understand the technology's fundamental principles and mechanics to effectively use it. The book itself is extremely dense. The content of the book is "only" 324 pages long but covers a large amount of ground in a good amount of detail. Definitely read in a quiet place free of interruptions with a strong cup of coffee. One shortcoming of the book is that it was written in 1997 so it doesn't cover TP implementations in Java (e.g. JTA, EJBs, etc.) but it was nice to finally find out what the heck IBM's CICS and IMS products are. Interestingly enough, I have never had to deal with complex transaction processing (i.e. two-phase commit) in my short IBM career. This is probably because I've worked on business-to-consumer (B2C) applications where only one data source is involved rather than a business-to-business system where multiple data sources are involved. I'll have to ask the B2B guys if they get heavy into two-phase commit or if it's not an issue. The reason I read this book is because I've always been a bit mystified by Enterprise JavaBeans (EJBs). When I joined IBM, I knew the word, but I was not familiar with such topics as object-relational persistence, object remoting, and transaction processing, so to me EJBs were simply things that took four classes/interfaces to do what I could do in one simple POJO. Ted Neward, in a very interesting web interview on the Serverside.com mentioned that he used to think EJBs were completely worthless, but during the process of writing Effective Enterprise Java came to realize that they were not worthless but rather over-marketed. He said that they should have been called Transactional JavaBeans rather than Enterprise JavaBeans because transactions are what EJBs did very well. So, hearing this from Ted I decided to read a book on fundamentals of transaction processing, so that I could understand EJBs better. Now that I've read all about TP principles, I pick Richard Monson-Haefel's book again, and all of a sudden EJBs start to make a lot more sense.

Back To Top