tfgrid/info_mydigitalself
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

...

Browse Source
This commit is contained in:
despiegk
2024-02-29 02:39:24 +03:00
parent f42e546af1
commit c741303fff
4 changed files with 23 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
problems/painkiller/actor_based_approach.md
View File

@@ -0,0 +1,7 @@
## OurDigital Self Actor Driven Approach
![](img/twin_model.png)
WITH OurTwin, there is an 'actor' driven pattern instead of a model first pattern. In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root.
The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes.

7
problems/painkiller/onion_layers.md
View File

@@ -23,10 +23,3 @@ The problem here is that individual systems are trying to redo things better, ho
One way to go around this has been to use Enterprise Message Bus: Controlling how models talk to each other by pre-defining the messages exchanged. But this does not solve the problem at the root.
## OurTwin Scenario
![](img/twin_model.png)
WITH OurTwin, there is an 'actor' driven pattern instead of a model first pattern. In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root.
The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes.