wagnerblog.com

Paul Stovel in his post on The Domain Tree describes the similarities between concepts listed in Domain Driven Design by Eric Evans and some aspects of WPF. Nice analogy. The part that had me tweak my ears , so to speak, is the application architecture tree toward the bottom of the post. I know this maybe counter intuitive, but I wonder what would happen if you bundled various Gateways (as listed in that tree) into a service and had the app consume that. This follows an idea I learned a few years ago from Ben Wilson, a programmer with Princeton Consulting and one of the smartest guys I’ve ever met. Essentially the notion is to provide various parts of an architecture as services within an app. In some cases the services may even be interrelated in the way a logging service might use a data access service. The whole point of all this being the idea to keep the connection area between services and application concentrated in one spot. Picture an hour glass shape. Each area present major functionality and the connection between them is kept very small. In our case it was done via Service Providers and Dependency Injection. We could swap out an entire service by changing the providersetting in the config. And since the service was instantiated via DI, there werent a bunch of references strewn throughougt the consumer code requiring all sorts of refactoring if another service was to be used instead.