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/022920240849 - Layered Architecture.md | |
| parent | 93d36010a9d54bca1fdcaf1f4c99e6981aaf41bc (diff) | |
lowercase dirs
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 |