Tohuwabohu excorcism

User Tools

Site Tools

Trace:
domain_driven_design

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
domain_driven_design [2023/11/21 09:57] – skipidardomain_driven_design [2023/11/21 19:13] (current) – [DDD & Microservices] skipidar
Line 32: Line 32:
  
  
-==== DDD &  Microservices =====+==== DDD & Microservices ===== 
 + 
 +=== Overview ====
  
 DDD has two distinct phases. DDD has two distinct phases.
Line 49: Line 51:
  
  
-== Strategic Design ==+=== Strategic Design ===
 In strategic DDD, you are defining the large-scale structure of the system. In strategic DDD, you are defining the large-scale structure of the system.
  
-== Tactical Design ==+=== Tactical Design ===
  
 Tactical DDD provides a set of design patterns that you can use to create the domain model.  Tactical DDD provides a set of design patterns that you can use to create the domain model. 
Line 59: Line 61:
 |Value Objects|are identified by their values. Like Address might be one. And re-created rather than copied.| |Value Objects|are identified by their values. Like Address might be one. And re-created rather than copied.|
 |Aggregate |<wrap>  |Aggregate |<wrap> 
-The purpose of an aggregate is to model transactional invariants. Things in the real world have complex webs of relationships. \\ \\ **Example:** Customers create orders, orders contain products, products have suppliers, and so on. If the application modifies several related objects, how does it guarantee consistency? How do we keep track of invariants and enforce them?+The purpose of an aggregate is to model **transactional invariants**. Things in the real world have complex webs of relationships. \\ \\ **Example:** Customers create orders, orders contain products, products have suppliers, and so on. If the application modifies several related objects, how does it guarantee consistency? How do we keep track of invariants and enforce them?
 </wrap>| </wrap>|
 |Services|In DDD terminology, a service is an object that implements some logic without holding any state.  \\ \\ Evans distinguishes between **domain services**, which **encapsulate domain logic**, and **application services**, which provide **technical functionality**, such as user authentication or sending an SMS message. Domain services are often used to model behavior that spans multiple entities.| |Services|In DDD terminology, a service is an object that implements some logic without holding any state.  \\ \\ Evans distinguishes between **domain services**, which **encapsulate domain logic**, and **application services**, which provide **technical functionality**, such as user authentication or sending an SMS message. Domain services are often used to model behavior that spans multiple entities.|
Line 68: Line 70:
  
  
 +
 +Overview of the process
 +
 +{{https://raw.githubusercontent.com/alfrepo/blog/main/content/docs/notes/article00016/ddd-process.drawio.png}}
  
 ==== Single micro-service (called "app" in 12-factor app model) architecture ==== ==== Single micro-service (called "app" in 12-factor app model) architecture ====
domain_driven_design.1700560657.txt.gz · Last modified: by skipidar