Skip to Content

Changes for page eMagiz State Generation

Last modified by Erik Bakker on 2024/08/13 12:05
From version 16.1
edited by Carlijn Kokkeler
on 2023/07/07 14:01
Change comment: There is no comment for this version
To version 14.1
edited by Carlijn Kokkeler
on 2023/07/07 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,7 +51,7 @@
51 51  
52 52  In the following, real-life implementations are given on how eMagiz State Generation has been realized through enrichment, aggregation, change detection, and duplicate detection.
53 53  
54 -==== 6.1 Enrichment ====
54 +==== 6.1 Enrich ====
55 55  
56 56  Company A works with a backend system based on ID/Name combinations. These are different for each implementation, and can be retrieved through a unique API. A difficulty that arises, is that some APIs initially only return the IDs. To prevent multiple calls to our backend system, the key/value pairs (ID/Name) need to be stored, such that these can be used in subsequent calls.
57 57  
... ... @@ -85,10 +85,10 @@
85 85  == 4. Key Takeaways ==
86 86  
87 87  * State generation concerns the generation of a stateful application or service
88 -* Stateful refers to the concept of storing a state of an object
88 + Stateful refers to the concept of storing a state of an object
89 89  * 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)
90 90  * 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
91 -* Stateful data can be generated through four main operations: enrichment, aggregation, change detection, duplicate detection
91 +* Stateful data can be generated through four main operations: enrich, aggregation, change detection, duplicate detection
92 92  
93 93  == 5. Suggested Additional Readings ==
94 94