Mon premier blog

Applying Domain-Driven Design and Patterns: With Examples in C# and .NET Jimmy Nilsson
Publisher: Addison-Wesley Professional

Domain-Driven Design is the best book I've read about designing enterprise software – though it is quite dense. This is yet another area I knew enough about to be dangerous but I certainly was no expert. There are many examples and discussions on i.e. Seconding The Pragmatic Programmer, Clean Code, TDD By Example, and Agile Principles, Patterns, and Practices in C#. As the first technical book of its kind, this unique resource walks you through the process of building a real-world application using Domain-Driven Design implemented in C#. DDD, Dependency Injection, CQRS, SOA, MVC but not so many examples on how to put them all together in a flexible way. I have also started on Patterns of Enterprise Application Architecture by Martin Fowler (it's a heavy read so I'm giving it a little bit of time). As it turns out, researching this topic wasn't easy. I have read the book Evans (Domain-Driven Design: Tackling complexity of the Heart of Software), Nillson book (Applying Domain-Driven Design and Patterns: Examples in C # and. With this said, Domain-Driven Design (DDD) is no exception. My goal: Develop modules that with little or no modification can stand on their own; Changing or reworking the UI should be as easy as possible (i.e. Applying Domain-Driven Design and Patterns: With Examples in C# and .NET “[This] is a book about design in the .NET world, driven in an agile manner and infused with the products of the enterprise patterns community. The UI should do as little as possible, and be "stupid"; Use documented patterns and principles. NET books = Framework Design Guidelines and CLR via C#.