Applying Domain- Driven Design and Patterns With Examples in C# and . NETI had a chance this weekend to start reading Jimmy Nilsson. The main focus of the book is on the value of a domain model and the implementation of the domain layer using Domain- Driven Design. However, he is also touching on topics which are the subjects of many books, topics like: Test- Driven Development, Refactoring, OOP, and Design Patterns. You don’t have to know or care about Test Driven Development or Refactoring to appreciate the book, but a good understanding of design patterns and OOP would be rather valuable. Even Jimmy mentions this . There are a lot of little notes and tangents, but not enough to be distracting. This is almost unavoidable as this is a complicated subject and I can . Hence, a quick note or tangent to better clarify or define a subject is taken to help those who perhaps need it, but doesn’t distract those who are already familiar with the concept. Jimmy’s style here is to discover the domain layer as if building one for the first time. You are essentially a fly on the wall of his brain, listening to his thoughts as he tries to cope with the building of the domain objects and when to introduce the infrastructure pieces of the domain layer ( factories and repositories ) using TDD. During this time he is also trying to 1) wrestle with how to avoid persistence, 2) discuss a number of design patterns in play, and 3) approach/handle the number of solutions and their tradeoffs that occur in every application. My only concern this far ( Chapter 8 ) is that persistence has been reduced to . This is great in that we shouldn’t be distracted by it, but bad in that we know it is a dark cloud that hovers above our heads. Jimmy has also introduced this concept of a Workspace ( IWorkspace ) that is injected into the Repository and is a database abstraction layer that handles the unit of work ( transactions ), but we haven’t seen much of it. To be fair, however, Chapter 9 is entitled . In my opinion it is a must have companion to Domain- Driven Design by Eric Evans, because it offers up the missing ingredient – how to implement the domain model using C# and . NET. In my humble opinion it is also an easier read, as I remember being overwhelmed by Domain- Driven Design by Eric Evans when I first read it. Jimmy’s book has a real- world, pragmatic feel to it that doesn’t claim to be the end all answer and a solution without tradeoffs. Net Domain-driven Design With C# ConvertHe is providing us another tool in our toolbox, and I look forward to the rest of the book. Some interesting community resources that may be of value as you work through the book. Another project type where you can easily confuse the roles of each layer is ASP.NET WebForms with. 17 Responses to A model.NET web service based on Domain Driven Design. Domain-Driven Design, C# und Windows Azure. Buy NET Domain-Driven Design with C#: Problem, Design, Solution (Programmer to Programmer) by Tim McCarthy (ISBN: 9780470147566) from Amazon's Book Store. Free UK delivery on eligible orders. In the post I would like to help folks who want to improve their design skills and way of thinking by introducing in the Domain Driven Design (DDD) and provide a set of resources which I find useful. Microsoft Visual C# MVP 2008-2012; Codeproject MVP 2008-2011. Apache Isis is a Java framework for developing domain-driven and RESTful applications using the Naked Objects. Designing the Domain Model 56. Samples for Domain Driven Design. I am still looking for the Alt.Net sample application if anyone knows where to find it?NET Domain-Driven Design with C#: Problem-Design-Solution; Domain Driven Design. Problem - Design - Solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2016
Categories |