Skip to Content

Changes for page H2 Database, Function

Last modified by Danniar Firdausy on 2024/09/16 15:49
From version 29.1
edited by Erik Bakker
on 2022/08/25 12:21
Change comment: There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2022/08/25 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,8 +23,6 @@
23 23   ** Holds data in case the queue (the onramp) cannot be reached
24 24   ** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
25 25  
26 -
27 -
28 28  == 3. H2 Database, Function ==
29 29  
30 30  When you utilize the messaging platform you are bound to see this component automatically appear in all your entries when you create those entries for the first time. However, we see that there is quite some confusion on what the function of this component is in the entry. In this microlearning, we will try our best to explain that function to you. In another microlearning, further down the road, we will discuss other applications of the H2 database.
... ... @@ -56,7 +56,7 @@
56 56  So what eMagiz gives you is a standardized database structure that temporarily stores messages (in case of connection issues). This is to ensure guaranteed delivery of the incoming message on the first queue in eMagiz (the onramp). As a bonus, the component helps you to smooth out the messages that are placed on the queue for further processing. With the help of this component, you prevent that when an external system offers 1000 messages within seconds all 1000 will end up on the queue at the same time. If that would happen you could run the risk of overloading your queue leading to larger issues (potentially even an 'out of memory' of the container).
57 57  
58 58  Hopefully, this microlearning will give you some context on why the H2 database is automatically generated by eMagiz in every entry and plays a crucial role in holding up to the promise of
59 -
57 +
60 60  == 4. Assignment ==
61 61  
62 62  Reflect on the choices made within various projects and see if you would, with what you know now, change the specific implementation.
... ... @@ -69,8 +69,6 @@
69 69   ** Holds data in case the queue (the onramp) cannot be reached
70 70   ** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
71 71  
72 -
73 -
74 74  == 6. Suggested Additional Readings ==
75 75  
76 76  If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
... ... @@ -77,8 +77,7 @@
77 77  
78 78  == 7. Silent demonstration video ==
79 79  
80 -As this is a more theoretical microlearning we have no video for this
81 -)))
76 +As this is a more theoretical microlearning we have no video for this)))
82 82  
83 83  ((({{toc/}}))){{/container}}
84 84  {{/container}}