-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add brief architecture outline
- Loading branch information
1 parent
272c2cf
commit f7f1a3a
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
<div align="center"> | ||
<img src="../../frontend/public/logo-full.png" alt="drawing" width="200"/> | ||
</div> | ||
|
||
# | ||
|
||
<div align="center"> | ||
Architecture outline | ||
</div> | ||
|
||
## Introduction | ||
|
||
This is an overview of the b[x] architecture for daemon components. This should make it easier for contributors to understand the specifics of this project's layout and design. | ||
|
||
## Core Components | ||
|
||
C++ daemon is developed with Domain-Driven Design principles in mind and split into 3 layers: | ||
|
||
- **Domain layer**: | ||
- `core/domain` - business logic (entities, value objects, repositories) | ||
- **Application layer**: | ||
- `core/application` - application layer that is used to orchestrate the business logic (DTOs, Services) | ||
- **Infrastructure layer**: | ||
- `persistence` - persistence logic implementation (databases, configuration) | ||
- `infrastructure` - infrastructure logic implementation (application layer implementations, networking, events, notifications) | ||
- `presentation` - presentation logic (http-controllers, filters, messages) | ||
|
||
The code also contains `utilities` directory. It's for various cross-cutting concerns or third-party libraries bindings. |