Java Transaction Design Strategies
Paperback, 116 Pages
Prints in 3-5 business days
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
Ratings & ReviewsLog in to review this item
9 People Reviewed This Product
Sep 22, 2011Great book for Java EE transaction! I could not find such good book on this area. It give me great help on my EJB 3 project. I should get this book earlier.
Dec 12, 2009Good 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.
Sep 24, 2009I 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
Aug 30, 2009"Great book on the transaction subject" the best material on this subject I have ever read, clear and concise
Apr 23, 2009"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
Aug 12, 2008"Re: Lacks effective writing" In truth I would have to disagree with this guy - I found the book well written, easy to read and understand, with plenty of humor thrown in as well. I actually enjoyed reading it, and due to the conciseness (sorry if this is *bad* grammer) I was able to read the whole book thru (something I simply do not have time for with other books). My advice: forget this review - the guy is probably referring to the wrong book!
Jan 9, 2008"Lacks effective writing" This book has the typical trademarks of technical manuals that are laced with technical details yet lack effective writing. Mr. Richards' grammar and sentence structure make the reader wonder what he/she has just read. This usually results in re-reading sentences or even full paragraphs. I have some suggestions for Mr. Richards’ to improve his writing skills. When beginning a new paragraph, Mr. Richards needs to pay more attention to placing the main idea in the first sentence. Also, reduce the use of excessive subordination and run on sentences. Eliminate the word "there" where the use of a noun will make sentences clearer. For example: "Fortunately, there is something we can do about system failures." could be restructured to "Fortunately, we can do something about system failures." Some sentences do not have a subject and the incorrect use of punctuation makes it difficult to understand meaning. I found inconsistent... More > subjects in some sentences. This sentence is an example: "Although I will be going into details about each transaction model, those particular chapters...” This sentence first introduces "I" as the subject, then out of the blue, with no transition, introduces "those particular chapters" as another subject. Also, I believe that "going into details" is incorrect grammar. An even more concise version of this sentence might be: "I will be detailing each transaction model". However, I do not know if my version of that sentence is the true meaning that Mr. Richards was trying to convey. I also do not believe that the use of the contraction "isn't" should be used in professional writing. "Isn't" may work well for a third grade storybook, but not for college level writing. Mr. Richards' third grade grammar is so distracting in this book that I found myself guessing quite a bit. Remember that your audience is probably well educated and reads at least at an 8th grade level. I would suggest a basic writing course and work your way up to college writing. And from your notes, it appears that you need a new reviewer for your initial manuscript.< Less
Oct 9, 2007"Re: Lacks effective writing" As indicated in my From The Author Posting, the book has been reviewed by many industry experts including Floyd Marinescu, Dr. Mark Little of JBoss (author of Java Transaction Processing), Stuart Dabbs Halloway (NFJS Speaker and author of Component Development for the Java Platform), Alan Beaulieu, (author of three best-selling books on SQL and Oracle), and many others in the technical and writing field. The book also went through a thorough editing and review process through Floyd Marinescu’s professional editing and publishing team. I am not sure which text you are referring to, but I doubt it is from Java Transaction Design Strategies.
Aug 10, 2006"A must have for anyone doing anything with Java and databases" This is a very concise book that you can read quickly but one of those books you'll want to keep on your shelf as a reference. If you are a Java developer and you do anything with databases then you need this book. Transactions are one of things that everybody uses but often don't have complete understanding of because it just seems so complicated. But after reading this book you'll realize that nothing can be farther from the truth, transactions now will see easy! Mark does a fantastic job making the seemingly complex into a very easy to understand guide. But at the same time this ain't no guide for dummies either. You'll appreciate the thorough description of the three transaction models: Local, Programmatic, and Declarative and XA transaction processing. You'll also learn when each should be used and some of the common pitfalls. The rest of the book covers some design patterns that you'll use in designing... More > your applications. One of the strong points of this book are the examples. Just about every example is shown in EJB 3.0 and in Spring. Both were new to me when I read this book but every single one of them made sense to me. But I can tell you I really can't wait to get going with EJB 3.0 and now I am intrigued to learn more about Spring. So the bottom line is that I highly recommend this book for anyone that does anything with Java and databases.< Less
There are no reviews for previous versions of this product
- C4Media Inc. (Standard Copyright License)
- First Edition
- Floyd Marinescu
- February 6, 2007
- Perfect-bound Paperback
- Interior Ink
- Black & white
- 0.5 lbs.
- Dimensions (inches)
- 6 wide x 9 tall
- Product ID
Your notification has been sent
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.
We were unable to complete your request.
We were unable to complete your request.
The page you are attempting to access contains content that is not intended for underage readers.
Please verify your birth date to continue.