From f76ece65673e93cabf3882ea182ad3d68db7f905 Mon Sep 17 00:00:00 2001 From: Chris Date: Mon, 15 Apr 2024 11:22:08 +1000 Subject: [PATCH] Update ADR --- ...use-domain-driven-design-tactical-patterns.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/adr/20240404-use-domain-driven-design-tactical-patterns.md b/docs/adr/20240404-use-domain-driven-design-tactical-patterns.md index 86580a89..9c2ae1be 100644 --- a/docs/adr/20240404-use-domain-driven-design-tactical-patterns.md +++ b/docs/adr/20240404-use-domain-driven-design-tactical-patterns.md @@ -1,17 +1,19 @@ # Use Domain-Driven Design Tactical Patterns -- Status: Pending -- Deciders: {{ TBC }} -- Date: 2024-04-04 -- Tags: ddd +- Status: Accepted +- Deciders: Daniel Mackay, Matt Goldman, Matt Wicks, Luke Parker, Chris Clement +- Date: 2024-04-04 +- Tags: ddd + +Technical Story: https://github.com/SSWConsulting/SSW.CleanArchitecture/issues/283 -Technical Story: {{ TECH STORY }} ## Context and Problem Statement -Currently, the template has is mostly geared towards building applications with an anemic Domain model. This is fine for simple applications, but not for complex applications with many business rules. +The current Clean Architecture framework relies on an anemic domain model, which simplifies initial development but increasingly hampers our ability to handle the complex interactions and business logic inherent in our domain. By incorporating Domain-Driven Design (DDD), projects with non-trivial logic can better accommodate complex workflows and business rule integrations without compromising maintainability or scalability. + +We would like to default to using DDD in the template and provide a good example of building applications in that manner. -Instead, we would like to default to using DDD in the template and provide a good example of building applications in that manner. ## Considered Options