Most Helpful Customer Reviews
|
|
11 of 11 people found the following review helpful:
5.0 out of 5 stars
Required Reading, December 5, 2003
If you are a Java/J2EE developer, reading this book will save you hundreds of wasted hours.
There are plenty of books on J2EE design patterns and best practices.
Bruce Tate goes well beyond these discussions and outlines the effectiveness of these strategies, antipatterns, and above all: alternatives. Simply put, this is the only book that puts J2EE into perspective.
Sales/Marketing have convinced developers that EJB is the "golden hammer" for enterprise solutions.
This book will enlighten you to creating effective J2EE applications without falling victim to market hype. It is my personal opinion that Bruce Tate is the most effective technical writer since Richard Stevens.
The writing is clear and to the concise, every page directly addressing common roadblocks in EJB development. For readers with a solid understanding of J2EE principles, this book will help you navigate around common pitfalls and outline effective solutions.
For less experienced readers, it will help you plan effectively. After reading a dozen J2EE books, Bitter EJB stands tall as "required reading".
|
|
|
12 of 13 people found the following review helpful:
5.0 out of 5 stars
When you want to know why, not just how., June 19, 2003
By A Customer
Bitter EJB couldn't have come at a better time for me. My development team is at a crossroads. Having developed a reasonably complex web-based model-view-controller architecture from scratch in Java, we thought we knew everything. Then it hit us: scalability problems, transactional integrity questions, database portability nightmares... we were in trouble. Ah, but knowing all, we determined that a simple migration of some of our logic to Enterprise JavaBeans would solve everything. Or would it? We started thinking: Are EJBs really better than JDO? Or home-grown solutions? How about JMS? Does it let us scale too? And what's with these Message Drive Beans? If we go EJB, do we use CMP? Hey, we hand-tuned a lot of JDBC code... aren't we going to see a performance degredation? Why would we choose Entity Beans over Session Beans or the reverse? How do we tackle the complexities of building and testing these components? We read the JavaDocs and specs, but we still had lots of questions, and not a lot of informed answers. Suddenly, we didn't feel so smart. At all. Thankfully Bitter EJB tackles these issues and more with humor and insight. There are plenty of good books that tell you how to build an EJB or use a message queue from Java. Instead of regurgitating the mechanics, this one tells you the why, why not and when to's of developing with EJBs and related technologies. You won't find a lot of EJB cheerleading in these pages, but rather a whole lot of unbiased, intuitive advice that will help you make the right decisions for your environment, product, team and goals.
|
|
|
11 of 12 people found the following review helpful:
5.0 out of 5 stars
They've been there, and done that, July 29, 2003
This book is a must-have for the serious J2EE developers. For example, many teams realize in EJB development that entity beans are overkill and complex enough to really drag a project down, yet very few books tell you this. Bitter EJB is the exception - it gives tried and true advice from those that have really been there and worked through the issues. In my extensive J2EE development experience I have learned the hard way many of these antipatterns. Do yourself a favor and don't learn these pitfalls the hard way - let Bruce, Mike, Bob, and Patrick join your team and steer you away from common mistakes, and towards best practices.
|
|
|
Most Recent Customer Reviews
|
by Bruce Tate
by Craig Walls
