Changes for page eMagiz State Generation

Last modified by Erik Bakker on 2024/08/13 12:05

From version 2.1
edited by eMagiz
on 2022/06/13 09:31
Change comment: There is no comment for this version
To version 3.2
edited by Erik Bakker
on 2022/06/13 14:05
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +fundamental-stateful
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,7 +1,4 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -<div class="doc">
1 +{{container}}{{container layoutStyle="columns"}}(((
5 5  
6 6  
7 7  
... ... @@ -11,9 +11,6 @@
11 11  
12 12  Should you have any questions, please get in touch with academy@emagiz.com.
13 13  
14 -* Last update: March 7th, 2022
15 -* Required reading time: 10 minutes
16 -
17 17  == 1. Prerequisites ==
18 18  
19 19  * Take a closer look at the Fundamentals for Messaging, API Gateway and Event Streaming
... ... @@ -66,8 +66,8 @@
66 66  
67 67  The state store is implemented inside the eMagiz runtime using the H2 database for now. For time related operations another technology is used (Esper), and the functionality is only available on Docker based runtimes (to be release end Q2 2022). You wil find the specific Stateful components inside the Flow Designer as we use in eMagiz to model the flow. Aligned with the general concept of low-code developnment in eMagiz. For State store models, the current data modeling capabilities will be used.
68 68  
69 -===== Practice =====
70 70  
64 +
71 71  == 4. Key takeaways ==
72 72  
73 73  * Stateful refers to the concept of storing a state of an object
... ... @@ -74,7 +74,7 @@
74 74  * Storing a state is different compared to data in transit which is often refered as stateless data (eMagiz doesn't store or update the data when sending across)
75 75  * Stateful can be applied across all patterns in eMagiz and is embedded into the platform in such a way that it provided the same user experience
76 76  
77 -<p align="center">[[image:ffundamental-stateful-1.png||]]</p>
71 +[[image:Main.Images.Fundamental.WebHome@ffundamental-stateful-1.png]]
78 78  
79 79  
80 80  
... ... @@ -86,8 +86,4 @@
86 86  
87 87  N/A
88 88  
89 -</div>
90 -</div>
91 -</div>
92 -
93 -{{/html}}
83 +)))((({{toc/}}))){{/container}}{{/container}}