Comments on: Architecture vs. Infrastructure http://blog.springsource.com/arjen/archives/2005/03/02/architecture-vs-infrastructure/ A blog about programming in .NET and Java Sun, 05 Jul 2009 03:17:31 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Jim Goodman http://blog.springsource.com/arjen/archives/2005/03/02/architecture-vs-infrastructure/comment-page-1/#comment-75 Jim Goodman Sat, 04 Jun 2005 11:02:09 +0000 /?p=28#comment-75 <p>I tried NEO two years ago. I found it clunky and couldn't understand how it's an object-relational tool. It doesn't support inheritence, and the way it handles many-to-many relationships is a total cop out. We had to munge our domain model to suit the limitations of the tool, which surely defeats the object (if you'll excuse the pun!) It generated all the code into a single file, which took ages and sometimes didn't work at all. Trying to evolve our domain model in a test-driven way was seriously difficult. It was a major pain to work with, and we threw it out after 3 weeks and decided to hand-roll our persistence layer - which worked out much cheaper in the long run, and resulted in a domain model that actually matched the analysis model. Since then, I've used NHibernate, which was a dream in comparison - though i'm keen to find out what the new WinFS implementation looks like for ObjectSpaces. With much better competition out there, and even better on the way, maybe the developers should just bin NEO?</p> I tried NEO two years ago. I found it clunky and couldn’t understand how it’s an object-relational tool. It doesn’t support inheritence, and the way it handles many-to-many relationships is a total cop out. We had to munge our domain model to suit the limitations of the tool, which surely defeats the object (if you’ll excuse the pun!) It generated all the code into a single file, which took ages and sometimes didn’t work at all. Trying to evolve our domain model in a test-driven way was seriously difficult. It was a major pain to work with, and we threw it out after 3 weeks and decided to hand-roll our persistence layer - which worked out much cheaper in the long run, and resulted in a domain model that actually matched the analysis model. Since then, I’ve used NHibernate, which was a dream in comparison - though i’m keen to find out what the new WinFS implementation looks like for ObjectSpaces. With much better competition out there, and even better on the way, maybe the developers should just bin NEO?

]]> By: Arjen http://blog.springsource.com/arjen/archives/2005/03/02/architecture-vs-infrastructure/comment-page-1/#comment-50 Arjen Wed, 16 Mar 2005 08:55:06 +0000 /?p=28#comment-50 <p>POCOs are definately on the radar, though at the moment, I cannot say if and how we are going to implement them.</p> <p>However, inheriting from a base class like the <code>EntityObject</code> also has its advantages. For instance, there is always an <code>ObjectContext</code> available for you to use.</p> POCOs are definately on the radar, though at the moment, I cannot say if and how we are going to implement them.

However, inheriting from a base class like the EntityObject also has its advantages. For instance, there is always an ObjectContext available for you to use.

]]> By: Paul Gielens http://blog.springsource.com/arjen/archives/2005/03/02/architecture-vs-infrastructure/comment-page-1/#comment-47 Paul Gielens Wed, 16 Mar 2005 06:40:02 +0000 /?p=28#comment-47 <p>Interesting pov, one with which I mostly agree. I was wondering what your thoughts are on supporting POCO (like Mats NPersist <a href="http://www.npersist.com/home/Default.aspx">http://www.npersist.com/home/Default.aspx</a>) in Neo.</p> Interesting pov, one with which I mostly agree. I was wondering what your thoughts are on supporting POCO (like Mats NPersist http://www.npersist.com/home/Default.aspx) in Neo.

]]> By: The Ancient Art of Programming » Spring and the Behavioral Domain Model http://blog.springsource.com/arjen/archives/2005/03/02/architecture-vs-infrastructure/comment-page-1/#comment-71 The Ancient Art of Programming » Spring and the Behavioral Domain Model Tue, 30 Nov 1999 00:00:00 +0000 /?p=28#comment-71 <p>[...] ent of a behavioral domain model. I wrote about the advantages of a behavioral domain in a <a href="http://arjen.jteam.nl/index.php/archives/2005/03/02/architecture-vs-infrastructure/">previous post</a>, but since that post was about .NET, I’ll [...]</p> [...] ent of a behavioral domain model. I wrote about the advantages of a behavioral domain in a previous post, but since that post was about .NET, I’ll [...]

]]>