I am ashamed to say this, but I have to do it, I have not worked with the ORM. I actually have NHibernate I'm considering because it is the most mature product. Out of the net (Please correct me if I am wrong) Now, this is the thing that we have a large e-commerce / booking system, in which SQL Server is the main integration point, which has many business logic is. Now - obviously - this architecture is something that wants to get away from us, and we are doing this for a while, by slicing the piece. So, my real question is how is it possible to start using NHibernate for new features and not returning and mapping all legacy materials? Is this type of introduction and ORM supported, and if so, would you recommend it?
It will depend on whether the "currently friendly" NHibernate is "How To Expose Your Existing Database" NHibernate Single Column likes the primary key (if they all have the same name as "id") as much as I know, so many ORMs are stored very messy. Do you think that you are going to get data from back and forth to DB to define your transfer object?
There is nothing to be embarrassed for BTW. ORM is a nonsense but you are trying to find it correctly.
Comments
Post a Comment