# 50 - Introduction to NHibernate: What does NHibernate bring to the table


9/29/2008
Level: Beginner
Tags: NHibernate ORM
Comments: (4)
Author:
Chad Myers
 
Presented By:
Ideavine.net


In this episode, you will learn about the reasons why you might use an Object/Relational Mapper (ORM). You will also hear why NHibernate is a particularly good ORM, when it is appropriate to use NHibernate and when it is NOT appropriate to use NHibernate. Finally, you will hear why you might choose NHibernate over the ADO.NET Entity Framework and Linq2Sql and when and might not choose it.
Click here to Watch this Episode

Download (12.61 MB) (10:54) (1440x900)
Download (8.70 MB) (10:54) (960x600)

Links/Resources:


Comments: (4)

Damon Wilder Carr said....

NOTE: Rant factor 3 (on a scale of 5)

Let's first set the context where it matters: those who pay us most of the time.

  • ORM is a mandate full stop for most applications
  • Not for why many think.

ORM is a mandate only as much as it gets developers and domain experts on the same page where there is no distinction. This is where I am forced to be today in global software and thank god it has arrived. Anything less is either specialized work or waste for the most part.

Stakeholders want DOMAIN solutions not technical. Have you had a domain expert ask for a few MS shaved off a yet to be deployed service? So why are you working on it?

 

As developers it should not suprise you that for anything non-commercial and interesting I have see in the last six months, you are expected to be every bit the domain experts as all 'conceptual excuses' are gone.

 

This is good. Ah.. Optimization you say? Google 'Premature Optimization'. I have nothing to add.

Not meant nasty here but our profession has changed. I live this change and am alarmed at my collegues who never both to recognize it.

 

Now being self-indulgent, I love the bits and bytes of it all as much as anyone. Just make it explicit.

I want to make those trusting me to build, ss happy as can be and I have no idea how to do that now under the pressure of the 'no compromise' culture we live in wuuthout ORM and a lot of other obvious (yet scary in how underutilized they are) items like C.I./Mocks,, etc.

 

Ugh I am so tired of seeing that.

 

Damon Wilder Carr

http://blog.domaindotnet.com

 

 

 


10/2/2008 6:35:25 PM

Damon Wilder Carr said....

Applogies for my bad spelling..


10/2/2008 6:37:23 PM

Chad Myers said....

Damon, 

I'm not sure whether you're flaming me or applauding me, or making a side argument :)

 

Flame.) I apologize if I've upset you
Applaud.) Thanks!, I think :)
Side-Arg.) I'm not sure I follow what you're trying to say. What's the point of your argument? I aplogize, but I'm having a hard time figuring out what you're trying to assert.

Thanks!


10/2/2008 10:20:31 PM

Sergio Pereira said....

I think Damon is just making a case for pragmatism and responsibility in software development. So yes, he's congratulating you, Chad,  somehow.


10/7/2008 5:35:36 AM


Name: *
Email (not displayed): *
Url:
Comments: *



Submit this story to DotNetKicks