Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Persistence in the Enterprise - Why should I read this book?

 
Cor Takken
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Mr. Barcia,

This question is not as stupid as it sounds.. but please do read the whole entry.

Since in most enterprises the method of object persistence is already chosen, the only thing that this book will give me is either a headache because the wrong choice has been made (and I have to live with it) or a sigh of relieve because I made the right choice.

In the first case the chance of my company changing the plumbings of the enterprise system will only increase if the total sum of headaches in the company exceeds the amount of pain felt in the money-belt to correct the situation. In the second case the most I will get out of the book is a good feeling.

I admit that this is quite a bold statement and I hope that you can give examples of the added value of your book.

Kind regards,

Cor Takken

[ July 22, 2008: Message edited by: Cor Takken ]
[ July 22, 2008: Message edited by: Cor Takken ]
 
Roland Barcia
author
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the question. I disagree with the statement that 'most enterprises' have chosen. My visits to customers have shown otherwise. Some large companies have different development groups using different persistent layers.

In general, the first half of the book is focused on general concerns on building application that access data and it's not focused on any one technology. There is a focus on architecture, requirements, etc... Then, the second half of the book focuses on realizing those concerns with each technology we cover.

This book will help one make the right choices when building an application (whenn to use SQL based approach vs. ORM, when to use one type of mapping versus another, etc...)

Hope this helps
 
Geoff Hambrick
author
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The intro is titled "Why you should steal this book (ith apologies to Abbie Hoffman).

But that is not the real reason. Besides what Rolands covers, we have found that the questionaire in Chapter 4 is good for driving requirements gathering in new projects to insure that nothing is missed. Not all will apply of course to every project. But that, plus the details in the following chapters will help you better exploit the framework you have chosen.

Also, we have found that knowing why you chose a given framework will help you better understand if there are compelling reasons to switch to another one.

And if you take the hint in Chapter 10 about applying Pattern Based Engineering, you can often fill the holes in your current framework yourself...

Ok then, Geoff
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic