diff options
| author | Jasper Ras <jras@hostnet.nl> | 2024-08-21 16:22:08 +0200 |
|---|---|---|
| committer | Jasper Ras <jras@hostnet.nl> | 2024-08-21 16:22:08 +0200 |
| commit | f3711a93832df46dc245075df08b9ebfc05266e9 (patch) | |
| tree | 167c4c4a9bedd6b94392b20eb6e68bc38656d456 /Zettelkast/Notes/022920240849 - Layered Architecture.md | |
| parent | 26b2ee8fe95026e84bd1721910d575db72cc1b3f (diff) | |
forgot to commit for a while
Diffstat (limited to 'Zettelkast/Notes/022920240849 - Layered Architecture.md')
| -rw-r--r-- | Zettelkast/Notes/022920240849 - Layered Architecture.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Zettelkast/Notes/022920240849 - Layered Architecture.md b/Zettelkast/Notes/022920240849 - Layered Architecture.md new file mode 100644 index 0000000..d551132 --- /dev/null +++ b/Zettelkast/Notes/022920240849 - Layered Architecture.md @@ -0,0 +1,7 @@ +Layered architecture is the art of dividing an application into different layers and applying rules to decide which code goes to which layer. +Examples of layered architecture are MVC. + +Another example is: +- Business layer ([[290220240839 - Domain Modeling]]): Encapsulates all business logic +- [[290220241412 - Service Layer]]: Encapsulate all application use-cases and manages orchestration before handing over to the domain layer. +- Interface layer: E.g Flask controllers, CLI, etc. They depend on the service layer.
\ No newline at end of file |