Browse by Tags
All Tags »
Design »
.NET (
RSS)
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...
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...
I had the pleasure to experience Niclas Nilsson’s passion for Ruby last week in Switzerland. Niclas presented Ruby on Rails at the Expo-C conference and facilitated the Ruby on Rails: A Kickstart at OOPSLA . He convinced me to give Ruby and Ruby...
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...
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....
Last week while giving my Principles and Patterns talk I received lost of positive feedback. In the first part I explained the history of principles and patterns, usage guidance, and gave book tips. In the second part I demonstrated the State Pattern...
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...
More Posts