Differences

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

--- domain_driven_design [2023/11/21 12:32] – skipidar
+++ domain_driven_design [2023/11/21 19:13] (current) – [DDD & Microservices] skipidar
@@ Line 61: / Line 61: @@
 |Value Objects|are identified by their values. Like Address might be one. And re-created rather than copied.|
 |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>|
 |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 70: / 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 ====