ORM, Workflow, Modelling. What do they have in common?

Well they are three areas that seem to have been in transition for ever. Especially in the Microsoft world.

So I decided to take a closer look and I’m starting with ORM, Object Relational Mapping which is the way to access data today. Like it, or not, it is generally the preferred way today.

A great staring point is Eric Nelson’s session which is apparently already from March: http://www.infoq.com/presentations/ORM-LINQ-Entity-Framework-Eric-Nelson

Here’s what I remember: Link to entities (part of ADO.NET Entity Framework) is our strategic technology. This is Microsoft’s and probably your long term bet. Why?

- It is not just there for SQL Server

- Microsoft is investing in this, see for instance the ADO.NET Entity Data Model Designer (http://msdn.microsoft.com/en-us/library/cc716685(VS.100).aspx)
Cc716685.3e6b487a-232e-4904-8ce1-52033a9746d6(en-us,VS.100).gif

- Microsoft is using it in other Microsoft products (SQL Data Services…)

- There are plenty partners building on it (IBM, OpenLink, DevForce, LLBLGen v3…)

 

Here is Eric’s page with resources on the Entity Framework. Be sure to check it out! http://geekswithblogs.net/iupdateable/archive/2009/09/23/entity-framework-4.0-resources-ndash-documentation-links-best-blog-posts.aspx