Paul Gielens:ThoughtsService

You know I actually bought (50$ is a big word for bought especially with the euro/dollar rate at peak as of today) WilsonORMapper and I must admit that I kind of like the way it works. Not to complex, not to simple.

I'll post something on my weblog about what I like especially about this one in contrast to some of the open source (NHibernate/Gentle) OR/Mappers which I have used. I still need to try out Frans' LLBLGEN someday to say how that one stacks up.

Have you had any experience with some of the products listed on that page?

Cheers,

Waseem

As a matter of fact I have. I’ve started out with LLBLGen which isn’t much of an object relational mapping tool. I’ve worked on a framework written by a Dutch company which has never released it to the public. At that time there where no serious (or stable) products available so we decided to write one ourselves. I’ve used Entity Broker 2003 for a proof of concept when I found out about Neo. Neo is my personal favourite. Neo is high quality, open source, active and supports domain driven development (or MDA). We use LLBLGen Pro on my current project (decision was made long before I came) and it’s turning out great. One thing I dislike about LLBLGen Pro is that you start out with your data model. It’s just plain impossible to get your data model right on the first go. Developers with a more data centric approach and feel comfortable discussing business problems on top of a ERD diagram should go in this direction. I’d rather modify my domain (talk the domain language as Eric Evens puts it in his latest title) and let NVelocity generate both the data and domain model schema. This is what Neo actually does.