![]() That said, developers seem to have a hard time grasping it. Domain Driven Design is actually pretty simple. To try and clear up some of the confusion around DDD, I am intending to start a series of short blog posts, covering aspects of DDD and trying to demystify it. As a buzzword, DDD is in danger of being corrupted like many other good software practices. As a book and methodology, DDD is an excellent way to approach complex software problems, and make them far more understandable and manageable. 20įoreword There is a lot of interest in DDD recently, both in the book, and in the methodology, and in the buzzword. 18 So What Are the Characteristics of a Good Domain Service?. 18 Shouldn’t Logic Be on the Entities Directly?. 16 Restrictions on Aggregates and Aggregate Roots. 16 So What is the Point of an Aggregate?. ![]() ![]() 14 And We Put These Things Into Repositories Right?. 13 So Entities and Value Objects Just Store Data?. 13 Hey, I’ve Heard of These, We Have Them in. 11 Does This Mean We Have More Than One Set of Data?. 11 What Does CQS Mean at an Architectural Level. 10 Command Query Separation as an Architectural Concept. 9 Where Does Persistence Ignorance Appear in DDD?. 9 What is Persistence Ignorance and Why Does it Matter?. 8 Surely Bounded Context’s Must Interact?. Domain Driven Design Step by Step Guide Casey Charlton 2009 ( )Ĭontents Foreword.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |