How it is different : Persistence in the Enterprise

[Dyann Sri]

How it is different " Persistence in the Enterprise : A Guide to Persistence Technologies " from other related books

[Geoff Hambrick]

We take an end-to-end view of persistence in enterprise applications, from the business drivers to the functional and non functional requirements. The first part of the book gives the background to understand the questions you should ask, the kinds of answers you tend to get, and the ramifications of each in terms of tradeoffs. From this we create a questionnaire that becomes a template for evaluation that we use to analyze five different frameworks, and which you can also use to drive your selection criteria. This same template is used in the summary chapter to give a side by side comparison.

As far as I know, no other book takes this kind of "wholistic" view.

Ok then, Geoff

[Roland Barcia]

Thanks for the post. In addition to Geoff's comments, many books on persistence cover the "How do I use?" Our book is more along the lines of "Why and When" to use which framework of feature in the framework?

[Cameron Wallace McKenzie]

This is actually a great book for Java architects to have by their side.

Understanding the various persistence mechanisms is one of the key skills architects need to have these days, as persistence is no longer a debate about EJBs or not.

I very much recommend anyone dealing with new systems to have a copy of this book by their side.

-Cameron McKenzie

[Gregg Bolinger]

Originally posted by Cameron Wallace McKenzie:
as persistence is no longer a debate about EJBs or not.

I would argue that point. EJBs or not is still a very lively debate. It should be a debate every time you start talking persistence. No magic bullet you know.