diff options
author | Jasper Ras <jras@hostnet.nl> | 2024-11-23 11:30:28 +0100 |
---|---|---|
committer | Jasper Ras <jras@hostnet.nl> | 2024-11-23 11:30:28 +0100 |
commit | 1f1423fdb8d4e2928768ffa33a6ad2b59c75e82e (patch) | |
tree | 67d94f0d821a053aca0e7c8a7ffb6c369047aa14 /Zettelkast/Notes/290220240839 - Domain Modeling.md | |
parent | 93d36010a9d54bca1fdcaf1f4c99e6981aaf41bc (diff) |
lowercase dirs
Diffstat (limited to 'Zettelkast/Notes/290220240839 - Domain Modeling.md')
-rw-r--r-- | Zettelkast/Notes/290220240839 - Domain Modeling.md | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/Zettelkast/Notes/290220240839 - Domain Modeling.md b/Zettelkast/Notes/290220240839 - Domain Modeling.md deleted file mode 100644 index 9fe7f7f..0000000 --- a/Zettelkast/Notes/290220240839 - Domain Modeling.md +++ /dev/null @@ -1,5 +0,0 @@ -Domain modeling can be used to define the business layer in a [[022920240849 - Layered Architecture]]. This is all the business logic. It should be easy to understand and easy to change as this is the code that changes the most frequently. - -A domain model can be comprised out of [[290220240843 - Value Object]], [[290220240842 - Entity]], Aggregates and functions that encompass domain procedures that do not necessarily fit in an object. -It is also fine to include Exceptions in the domain, e.g stock can go out of stock and thus when we would allocate an order it would raise an OutOfStock exception. - |