Paul Gielens:ThoughtsService

LINQ to make the Data Access Layer Irrelevant

LINQ will transform the architectures around us and make the traditional data access layer irrelevant. Kris Vandermotten wrote a few lines about this here and here .

Demo Code DDD vs. MS-TLSA

Tim McCarthy uploaded his slides and demo code for his talk on "Domain-Driven Design using the ADO.NET Entity Framework". Last year I wrote the article " Organizing Domain Logic " which compares Microsoft Three-Layered Services Architecture...

Aggregates, Services and Entities

Ayende’s example calculates the cost for an order. For this it needs the order lines associated with the order. Udi brings up an interesting fact about Ayende’s implementation. The order service knows a whole lot about the implementation details of the...

Process and Control SOA

I tried to commit to the simple rule “do not post a post on a post”, but now that Gregor has this excellent post on “ Validating Dynamic Systems ” on his blog. I’m going to say goodbye to the rule for now. Apparently Gregor...

Language Support for the Domain Model

While I was walking up the slopes with Frans to watch the World Championships Big air qualifications in Arosa, Switzerland during our annual Software Architecture Workshop, we talked about the support for Domain Model patterns in his product LLBLGen Pro...

Web Service Software Factory leaves a sour taste

Why do I spend so much time with the ADO.NET vNext bits? Udi just reminded me why with his post Web Service Software Factory – Data Access CRUD! Web Service Software Factory implements (or at least the generated code base does) the Three-Layered...

Organizing Domain Logic

In this article we compare the Microsoft Three-Layered Services Application [Microsoft TLSA] architecture against one by Domain Driven-Design architecture [Evans DDD] for organizing domain logic. For this purpose we use the Microsoft .NET Pet Shop 4 application as an example to explain the difference between these two approaches. It then gives some comments on what Microsoft has in store to better support the latter. This article is aimed at developers and architects who are trying to find better ways to capture the abstraction of the domain in their designs. It will help you if you have some knowledge in building enterprise applications on the .NET platform....

Applying the Application Layer in Domain-Driven Design

Peter Veentjer published his second post on Domain-Driven Design in which he questions the need for a Service Layer. First, the Service Layer is what Eric Evans calls the Application Layer. Let’s see what Eric has to say about this particular layer in...

Keeping the Domain Model free from Persistence Logic

A system with a complex domain model often benefits from isolating the domain objects from persistence logic. Your domain objects are then Plain Old CLR Object (POJO), or PI-O (Persistence Ignorance-Objects). In my case I want the decision about which...

Performance when using Object Relational Mapping

Sorry, object relational mapping has been discussed in detail over various message boards, architecture groups, newsgroups and whatnot. Every now and then real-life projects are still struggling. Most of today’s applications are developed with rich object...