Applying Domain-Driven Design and Patterns: With Examples in C# and .NET

Chapter 4. A New Default Architecture In the past, I've been pretty data-centric in my application architectures. Lately, this has gradually changed and my current default architecture is based on a Domain Model. This is why the title of thi...

The Basis of the New Default Architecture As I just said, my new default architecture is based on a Domain Model. We discussed Domain Models a lot in Chapter 1, "Values to Value," but let's discuss it here, also. Note Paul Gielens ...

A First Sketch To make it a bit more concrete, let's use a list of problems/features to discuss how some common design problems of an ordering application could be solved. I know, I know. The answer to how I would deal with the feature list with ...

Making a First Attempt at Hooking the UI to the Domain Model I once started describing a new architecture from the bottom up. I mean, I started describing it from the database. One of the readers told me in no uncertain terms that I should start t...

Yet Another Dimension So far in this chapter, I have mostly talked about the logical structure of the Domain Model, which is just one dimension of the picture, of course. There are others. I'd also like to discuss different execution styles for ...

Summary I know, you wanted the chapter to go on forever, but sadly it's come to an end. We've covered a lot of ground, discussed a "new" default architecture based on Domain Models to quite an extent, and also sketched how it can be used...