In practice various frequent decoupling scenarios exist. These scenarios can be categorized as follows:
- Calling/exposing domain functions to application
- Persistence of data
- Calling/exposing a webservice
- Showing data to customer facing applications
- Calling/exposing application functions
For every category examples exist of various complexity. We intend to cover examples of various complexity.
Each elaborated example is strongly supported by these theoretical principles and constraints:
- Principles of Clean Architecture
- Decoupling characteristics
- Blueriq tool possibilities
In the practical examples are the theoretical principles applied, and these ultimately lead to modelling patterns withing Blueriq. This is shown schematically below.
Examples
In the table below an overview of the available examples is shown.
| Decoupling category | Simple example (S) | Complex example (L) |
|---|---|---|
| Calling/exposing domain functions to application (1) | ||
| Persistence of data (2) | Persistence data (read/write) | |
| Showing data to customer facing applications (4) | Intelligent dialog for problem diagnosis | |
| Calling/exposing application functions (5) | Changing Personal Information |
The following examples concern knowledge automation and decision management:
- Domain: Loan to Income Calculation
- Domain: Housing policy
- Interface: Municipality Value List
- Interface: Input validation
- Interface: Intelligent dialog for problem diagnosis
Cross-Cutting Concern Example
Some concerns are called cross cutting as it plays a role in any layer of the architecture. Well-known examples include security and performance. As these concerns play the same rule in Blueriq, an examples has been prepared concerning security.
Overview
Content Tools