Comments for foofish.org http://foofish.org/blog the word "pragmatic" sounds funny if you think about it... Sat, 15 Oct 2011 06:25:09 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on NHibernate and Entity Framework Battle it Out in the Real World by Sergey http://foofish.org/blog/?p=57&cpage=1#comment-16489 Sergey Sat, 15 Oct 2011 06:25:09 +0000 http://foofish.org/blog/?p=57#comment-16489 Interesting experience. I found that this article is the most helpful to comapre EF 4 to nHiberante: http://xhalent.wordpress.com/2011/02/01/nhibernate-vs-entityframework-experience-from-the-real-world/#comment-158 There is one more point for consideration when choosing EF vs. nHibernate: EF can query SSAS OLAP cubes ( via SSAS Entity Framework Provider - www.agiledesignllc.com/Products ), and nHibernate cannot. It is important if you have large data volume (> 2 million of records) but still need your queries to execute very fast. Interesting experience.
I found that this article is the most helpful to comapre EF 4 to nHiberante:
http://xhalent.wordpress.com/2011/02/01/nhibernate-vs-entityframework-experience-from-the-real-world/#comment-158

There is one more point for consideration when choosing EF vs. nHibernate: EF can query SSAS OLAP cubes ( via SSAS Entity Framework Provider – http://www.agiledesignllc.com/Products ), and nHibernate cannot. It is important if you have large data volume (> 2 million of records) but still need your queries to execute very fast.

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Mike http://foofish.org/blog/?p=57&cpage=1#comment-11540 Mike Thu, 26 May 2011 07:06:51 +0000 http://foofish.org/blog/?p=57#comment-11540 I'm with Piglet: If you re-investigate the comparison nowdays you will find that Entity framework has come a long way since this article was initially published. Nhibernate has improved too, but it's hard for new ORM users to justify the learning curve when EF does a similar job out of the box and with better documentation. I’m with Piglet: If you re-investigate the comparison nowdays you will find that Entity framework has come a long way since this article was initially published. Nhibernate has improved too, but it’s hard for new ORM users to justify the learning curve when EF does a similar job out of the box and with better documentation.

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Pros and Cons of NHibernate | Robert Corvus http://foofish.org/blog/?p=57&cpage=1#comment-9758 Pros and Cons of NHibernate | Robert Corvus Sun, 10 Apr 2011 06:37:57 +0000 http://foofish.org/blog/?p=57#comment-9758 [...] vs Entity Framework: http://foofish.org/blog/?p=57NHibernate vs Entity Framework performance test: [...] [...] vs Entity Framework: http://foofish.org/blog/?p=57NHibernate vs Entity Framework performance test: [...]

]]> Comment on DDD and Aggregates by Richard Dalton http://foofish.org/blog/?p=47&cpage=1#comment-8105 Richard Dalton Thu, 10 Feb 2011 10:58:35 +0000 http://foofish.org/blog/?p=47#comment-8105 Everything depends on the specifics of a project, but...the following sounds reasonable to me. Line Item should be a Value Object, it should have no identity outside of the Order that it belongs to, therefore it should not have it's own repository. It should be impossible to simply load edit and save changes to a line item without the Order knowing about it. In fact being a value object Line Items should be immutable. What you really want to do is replace an existing line item with a different line item. That "replace" is an operation that should happen at the Order level. Everything depends on the specifics of a project, but…the following sounds reasonable to me.

Line Item should be a Value Object, it should have no identity outside of the Order that it belongs to, therefore it should not have it’s own repository. It should be impossible to simply load edit and save changes to a line item without the Order knowing about it.

In fact being a value object Line Items should be immutable. What you really want to do is replace an existing line item with a different line item. That “replace” is an operation that should happen at the Order level.

]]> Comment on DDD and Aggregates by Greg Young http://foofish.org/blog/?p=47&cpage=1#comment-6411 Greg Young Wed, 24 Nov 2010 01:38:36 +0000 http://foofish.org/blog/?p=47#comment-6411 "However, in practice you may need to deal with the line item by itself, for instance the “edit the line item” screen on a website." I think this is the crux of the issue. Do you actually know this? Aggregates are built up around invariants and where consistency boundaries lie. Very often editing a line item requires the entire order in order to validate whether the update to the line item is acceptable (consider a maximum total amount for an order or that you can only order x count of items that are on sale within the same order) HTH Greg “However, in practice you may need to deal with the line item by itself, for instance the “edit the line item” screen on a website.”

I think this is the crux of the issue. Do you actually know this? Aggregates are built up around invariants and where consistency boundaries lie. Very often editing a line item requires the entire order in order to validate whether the update to the line item is acceptable (consider a maximum total amount for an order or that you can only order x count of items that are on sale within the same order)

HTH

Greg

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Gareth Hayter http://foofish.org/blog/?p=57&cpage=1#comment-4132 Gareth Hayter Thu, 10 Jun 2010 03:02:41 +0000 http://foofish.org/blog/?p=57#comment-4132 A lot has changed since you first wrote this post! Anyway, Nhibernate now has a GUI designer which helps you create and maintain NHibernate projects: http://www.slyce.com Pity it wasn't around when your project started! A lot has changed since you first wrote this post! Anyway, Nhibernate now has a GUI designer which helps you create and maintain NHibernate projects: http://www.slyce.com Pity it wasn’t around when your project started!

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Piglet http://foofish.org/blog/?p=57&cpage=1#comment-3851 Piglet Mon, 10 May 2010 09:33:34 +0000 http://foofish.org/blog/?p=57#comment-3851 A tip: Before making a decision Nhibernate or Entity Framework 4.0 read this post (with ALL its comments). It sure helped me: http://ayende.com/Blog/archive/2010/01/05/nhibernate-vs.-entity-framework-4.0.aspx A tip: Before making a decision Nhibernate or Entity Framework 4.0 read this post (with ALL its comments). It sure helped me:

http://ayende.com/Blog/archive/2010/01/05/nhibernate-vs.-entity-framework-4.0.aspx

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Vanesa Barbosa http://foofish.org/blog/?p=57&cpage=1#comment-2525 Vanesa Barbosa Mon, 23 Nov 2009 14:21:35 +0000 http://foofish.org/blog/?p=57#comment-2525 Interesting blogs. Our development team must make the decision with VS2010, Nhibernate advise using? Interesting blogs. Our development team must make the decision with VS2010, Nhibernate advise using?

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Juan http://foofish.org/blog/?p=57&cpage=1#comment-2238 Juan Thu, 08 Oct 2009 04:35:45 +0000 http://foofish.org/blog/?p=57#comment-2238 Hi everybody. We had to make a choice some months ago, regarding the ORM mapping framework for our new project, it had around some 100 tables. Well, we tested like some 6 ORMs!, including EF. The fear we had with third party ORMs was that you leave something very importante in some other's hand and the possibility that the product could become obsolet due to a not more supported or bad supported product. Our EF team did a great job in our detached scenario using WCFs and EF in both client & server sides. After two months of hard work we made everything work fine using a special class for attaching detached entities (http://www.codeproject.com/KB/architecture/attachobjectgraph.aspx) now we have a faster development process due to sepparating our UI and BO layers from client to wcf server and created a generic Client service layer and WCF service layer for any kind of project, so we just add some dlls references and the communication channel is done! well, what else I can say. after some hard work, using .net 3.5, we are using EF in a detached scenario very elegantly (not using mar property as modified, hehe). Hi everybody. We had to make a choice some months ago, regarding the ORM mapping framework for our new project, it had around some 100 tables. Well, we tested like some 6 ORMs!, including EF. The fear we had with third party ORMs was that you leave something very importante in some other’s hand and the possibility that the product could become obsolet due to a not more supported or bad supported product.
Our EF team did a great job in our detached scenario using WCFs and EF in both client & server sides. After two months of hard work we made everything work fine using a special class for attaching detached entities

(http://www.codeproject.com/KB/architecture/attachobjectgraph.aspx)

now we have a faster development process due to sepparating our UI and BO layers from client to wcf server and created a generic Client service layer and WCF service layer for any kind of project, so we just add some dlls references and the communication channel is done!

well, what else I can say. after some hard work, using .net 3.5, we are using EF in a detached scenario very elegantly (not using mar property as modified, hehe).

]]> Comment on NHibernate and Entity Framework Battle it Out in the Real World by Arash http://foofish.org/blog/?p=57&cpage=1#comment-1684 Arash Thu, 25 Jun 2009 00:15:52 +0000 http://foofish.org/blog/?p=57#comment-1684 Look at Mindscape's LightSpeed product. It's a very easy to use ORM with full LINQ support, meaning your LINQ query will be translated into an appropriate SQL query. I don't think NHIbernate has that yet. Look at Mindscape’s LightSpeed product. It’s a very easy to use ORM with full LINQ support, meaning your LINQ query will be translated into an appropriate SQL query. I don’t think NHIbernate has that yet.

]]>