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.
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?
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services