Understanding how transaction management works in Java and developing an effective transaction design strategy can help to avoid data integrity problems in your applications and databases and ease the pain of inevitable system failures.
This book is about how to design an effective transaction management strategy using the transaction models provided by Java-based frameworks such as EJB and Spring. Techniques, best practices, and pitfalls with each transaction model will be described. In addition, transaction design patterns will bring all these concepts and techniques together and describe how to use these models to effectively manage transactions within your EJB or Spring-based Java applications.
The book covers:
- The local transaction model
- The programmatic transaction model
- The declarative transaction model
- XA Transaction Processing
- Transaction Design Patterns
Good book that thoroughly but briefly covers a recurring topic. Clearly differentiates between programming models (declarative versus programmatic). Identifies some of the subtler limitations of the EJB platform for supporting the programmatic transaction model. A good (and brief) description and comparison of XA. Overall a high return on your on investment for the time used to read the book.
I am writing this review to counterbalance the previous review, which is absurd. Java Transaction Design Strategies explains how to use transactions in Java and J2EE, with specific recommendations based on extensive real-world experience. See for yourself. Or, trust the irrelevant grammar advice from the previous reviewer, who believes in a discipline called discreet [sic] mathematics. buy degree | Corllins University
"Where's the UML?" Although there are some very noticeable grammatical and sentence structure issues in the first few pages, for the most part, these issues are resolved around page 11. In my brief scan of the book, I saw classes and methods mentioned in paragraphs. And when I saw the diagrams it was clear what class owned what responsibilities. However, when the author mentions the need to call certain methods based on certain conditions, I expected to see some UML. I saw instances where class diagrams, activity diagrams and sequence diagrams could have been extremely useful … and simple to put together. When I read the back of the book and saw Mr. Richards' credentials, I was even more confused about why a Senior IT Architect at IBM would not use UML diagrams. As a supposed leader in his field, should he not be setting an example for the use of standards? I feel, given the author’s substantial background, that this book could use some improvement not only grammatically,... More > but also with additional diagrams. Also, since this book was published on or around May 30, 2006, I would like to pose a question to the reviewer who indicates that he/she implemented Mr. Richards' design pattern(s) within 5 or 6 weeks. Maybe you're dealing with a small non-critical system. However, the systems that I have worked with in the past required that a change in the architecture necessitated a full analysis and design including risk assessment. This usually took a few months at minimum. All is dependent on the size of the system, but implementation could take another month or 6 months. Given the nature of the deployment (database transaction related), deployment may require a system shutdown. As we all know, system shutdowns are not easily coordinated in a large organization or with internet-based applications. Since the content of this book seems to be geared towards larger, enterprise applications / systems, I am wondering how you managed to get all this work done and debugged within 4-5 weeks?< Less
Lulu Staff has been notified of a possible violation of the terms of our Membership Agreement. Our agents will determine if the content reported is inappropriate or not based on the guidelines provided and will then take action where needed.
Thank you for notifying us. We will email you with the results and/or actions taken as a result of the investigation if you chose to receive confirmation.