The issues you are seeing aren’t caused by Domain Driven Design, but rather by a lack of separation of concerns. Domain Driven Design isn’t just about placing data and behavior together. The first thing I would recommend is taking a day or so and reading Domain Driven Design Quickly available as a free download from … Read more
Decorator uses Delegation, but in a very specific way. Delegation (or composition) is not as much a pattern as a general way to build complex behavior by coordinating use of several other objects. It’s often used in a set or static way. By “set or static” I mean something like this: class Delegator { private … Read more
According to Jon Skeet in Implementing the Singleton Pattern in C# the code you posted is actually considered as bad code, because it appears broken when checked against the ECMA CLI standard. Also watch out: everytime you instantiate your object with a new type of T, it becomes another instance; it doesn’t get reflected in … Read more
The DispatcherScheduler has been moved to the System.Reactive.Windows.Threading assembly. If you are using NuGet, it’s in Rx-WPF
In theory they are the same, it’s the intent that differentiates one pattern from the other: Decorator: Allows objects to be composed/add capabilities by wrapping them with a class with the same interface Adapter: Allows you to wrap an object without a known interface implementation so it adheres to an interface. The point is to … Read more
In my eyes, an Adapter and a Shim would be the same. A Facade on the other hand serves a different purpose. If you expect your client code to need to be able to pull back the curtain, so to speak, and access the underlying library without using your object model, that would be a … Read more
Yes, you should probably start off with pattern matching instead of the visitor pattern. See this interview with Martin Odersky (my emphasis): So the right tool for the job really depends on which direction you want to extend. If you want to extend with new data, you pick the classical object-oriented approach with virtual methods. … Read more
If you look at the first example at that Go Concurrency Patterns blog post, you’ll notice that they’re “deriving” their contexts from the Background context. That, combined with the Context and WithContext methods on your Request object, gives you what you need. I just figured this out (and it wasn’t my first run at reading … Read more
The Reactor pattern is used with worker threads to overcome a common scenario in applications: You need to do a lot of work eventually but you don’t know which work and when and creating threads is an expensive operation. The idea is that you create a lot of threads which don’t do anything at first. … Read more
The Service will use a Repository to retrieve an Entity and then call methods on it (the Entity) to perform the Command/task.