Changes for page eMagiz State Generation
Last modified by Erik Bakker on 2024/08/13 12:05
From version 28.1
edited by Erik Bakker
on 2024/08/13 08:04
on 2024/08/13 08:04
Change comment:
There is no comment for this version
To version 24.1
edited by Erik Bakker
on 2024/08/08 13:51
on 2024/08/08 13:51
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In this fundamental, we will explorethe concept ofstategeneration,itsbenefits,operations,andimplementation within thecontext ofreal-timedata processing. Thetextcoversvarious aspects, including enrichment,aggregation,changedetection,and duplicate detection, along withspecific usecases inthecontext of eMagiz State Generation.2 +In this fundamental, we'll take a look at the capability of eMagiz around storing a state of a data packet or message sent across the platform. 3 3 4 4 Should you have any questions, please get in touch with academy@emagiz.com. 5 5 ... ... @@ -57,7 +57,7 @@ 57 57 58 58 A state can most logically be created in a central place through which the data flows. The reason for this, is that such a place has all the required information flowing through its processes to generate stateful data. 59 59 60 -The state store is implemented inside the eMagiz runtime using varioussupportobjects.Once youhaveagreed on thelicenseyoucan findstore items in the store andcomponents 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.60 +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. 61 61 62 62 === 3.3 Use Cases === 63 63 ... ... @@ -104,8 +104,6 @@ 104 104 105 105 == 5. Suggested Additional Readings == 106 106 107 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] 108 -** [[State Generation (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.State Generation.WebHome||target="blank"]] 109 -* [[State Generation (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=2%2FMain.eMagiz+Academy.Microlearnings.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22state+generation%22||target="blank"]] 107 +N/A 110 110 111 111 )))((({{toc/}}))){{/container}}{{/container}}