NetTiers vs NHibernate vs Wilson OR Mapper

[mcquiggd]

Anybody used these tools / architectures...?

NHibernate seems to just do ORM mapping with an XML file that is as complicated as you want it to be... Wilson ORM is slightly more advanced I fell.. NetTiers makes use of the Enterprise Library and at first sight seems to offer more...

I'd like to hear peoples experience of either.... it seems to be a decision bewteen XML mapping, or reverse engineering a database schema.

[Cowboy Bob]

Anybody used these tools / architectures...?

NHibernate seems to just do ORM mapping with an XML file that is as complicated as you want it to be... Wilson ORM is slightly more advanced I fell.. NetTiers makes use of the Enterprise Library and at first sight seems to offer more...

I'd like to hear peoples experience of either.... it seems to be a decision bewteen XML mapping, or reverse engineering a database schema.

Being a Java guy, I've used the Java version of Hibernate. I tend to use it in conjunction with http://www.andromda.org/ (for which there's a version for .NET). That way it becomes less complicated to use - and less tedious in that there's no need to write all the niggly value objects or XML files.

Hibernate a great tool and is very mature on the Java side of things. Not sure about the .NET as I've never written a line of .NET code...

[TheMonkey]

I'm going to try NHibernate for a project but I get the feeling that it's going to be a too slow for a high traffic web site.

[Cowboy Bob]

I'm going to try NHibernate for a project but I get the feeling that it's going to be a too slow for a high traffic web site.

If you make sure all the indexes are in place in the DB, you'll be surprised. I don't think it's much slower than direct DB queries. After all, the time is usually taken up with the queries themselves anyway in a high-traffic site with a large DB.

[TheMonkey]

If you make sure all the indexes are in place in the DB, you'll be surprised. I don't think it's much slower than direct DB queries. After all, the time is usually taken up with the queries themselves anyway in a high-traffic site with a large DB.

That's what I was hoping. I have extensive caching stuff ready to drop in on the UI anyway so that should sort out the worst bits.