On Entities...

re: On Entities...

anoakes — Thu, 22 Jun 2006 06:37:21 GMT

Tim,

I agree with you that at the end of the day, data is king and I really appreciate what Microsoft has done. I would like to add though, that I feel being data centric also has its flaws. Whereas being behavior centric, which does have flaws also, has come to my attention lately. Data, though king, does deteriorate over time. It has also caused myself many problems with applications. The group I work with took a hard look at this problem and decided to shift our focus from being data minded to behavior minded and have seen some promising results. We live on business objects.

An Entity Data Model does have its benefits, but I feel it can also stifle progress. Just a thought.

LINQ, ADO.NET and Entities

Alex Barnett blog — Thu, 22 Jun 2006 07:57:05 GMT

In case you missed it, Somasegar (Microsoft's VP of Developer Division) blogged today about some of the...

re: On Entities...

timmall — Thu, 22 Jun 2006 08:44:17 GMT

Allen,

I agree that there are issues being purely data-centric or beavior-centric. I think that this is one of the internal conflicts that folks have all the time... are you doing OO if you do not encapsulate state and behavior for example.

Here are some random thoughts... data often outlives applications; in the move to mid-tier apps we often built new apps on top of the same persistent data. In the move to composite apps we see much of the same, building process oriented apps and rich clients that aggregate services but they are built on the same underlying data. My biased opinion is that often people who model in a behavior centric way compromise the ability for data to outlive the app. Some of the more flexible patterns are transaction script and manager style patterns which provide a separation of concerns between state and behavior. We can still provide meaningful domain models and OO infrastructure but the separation of concerns is often beneficial tactically and strategically.

I believe that as we move to more process oriented applications and late bound aggregations of service data we will see people start to embrace dynamic models with declarative intent in more of a functional flavor than an imperative flavor. Of course, to your point... if you are polarized too far to one side or the other [which I may very well be :) ] then you can get into world where the approach indeed can stifle progress... as my wife likes to tell me "everything in moderation".

re: On Entities...

anoakes — Thu, 22 Jun 2006 20:32:38 GMT

Tim,

My wife says the same thing! :)

I've been exploring the EDM and it does show promise. Maybe as it matures it could help bridge the gap between behavior and data. I know that I'll be using. Thanks for your thoughts back.

Allen

ADO.NET vNext - feedback so far

Data Access blog — Sat, 24 Jun 2006 07:50:18 GMT

Since announcing our ADO.NET vNext plans at TechEd last week, the team has been on the lookout for your...

ADO.NET vNext - feedback so far

ADO.NET team blog — Tue, 11 Jul 2006 20:34:23 GMT

(this post&nbsp;was originally posted here)

Since announcing our ADO.NET vNext plans at TechEd
...

New and Notable 104

Sam Gentile — Sun, 01 Oct 2006 09:34:25 GMT

You know what? Owning a pool really sucks-). Oh, it&rsquo;s great to go in but not a lot of fun spending

Tim Mallalieu s Blog On Entities | Cast Iron Cookware

Tim Mallalieu s Blog On Entities | Cast Iron Cookware — Fri, 12 Jun 2009 05:20:15 GMT

PingBack from http://castironbakeware.info/story.php?title=tim-mallalieu-s-blog-on-entities

Tim Mallalieu s Blog On Entities | pool toys

Tim Mallalieu s Blog On Entities | pool toys — Thu, 18 Jun 2009 11:50:25 GMT

PingBack from http://pooltoysite.info/story.php?id=6583

Tim Mallalieu s Blog On Entities | garden decor

Tim Mallalieu s Blog On Entities | garden decor — Fri, 19 Jun 2009 10:26:36 GMT

PingBack from http://gardendecordesign.info/story.php?id=4491