Changes for page H2 Database, Function

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

Content

...	...	@@ -5,9 +5,6 @@
5	5
6	6	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7	7
8		-* Last update: July 29th, 2021
9		-* Required reading time: 5 minutes
10		-
11	11	== 1. Prerequisites ==
12	12
13	13	* Basic knowledge of the eMagiz platform
...	...	@@ -21,13 +21,11 @@
21	21	The focal point of this microlearning will be to figure out why the H2 database is part of any auto-generated entry.
22	22
23	23	* The key aspects are:
24		- * H2 Database temporarily stores data
25		- * Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
26		- * Holds data in case the queue (the onramp) cannot be reached
27		- * Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
	21	+ ** H2 Database temporarily stores data
	22	+ ** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	23	+ ** Holds data in case the queue (the onramp) cannot be reached
	24	+ ** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
28	28
29		-
30		-
31	31	== 3. H2 Database, Function ==
32	32
33	33	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.
...	...	@@ -35,10 +35,10 @@
35	35	The focal point of this microlearning will be to figure out why the H2 database is part of any auto-generated entry.
36	36
37	37	* The key aspects are:
38		- * H2 Database temporarily stores data
39		- * Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
40		- * Holds data in case the queue (the onramp) cannot be reached
41		- * Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
	33	+ ** H2 Database temporarily stores data
	34	+ ** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	35	+ ** Holds data in case the queue (the onramp) cannot be reached
	36	+ ** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
42	42
43	43	As you probably noticed by now is that every time you create a new entry in eMagiz some components are automatically generated for you.
44	44
...	...	@@ -59,7 +59,7 @@
59	59	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).
60	60
61	61	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
62		-
	57	+
63	63	== 4. Assignment ==
64	64
65	65	Reflect on the choices made within various projects and see if you would, with what you know now, change the specific implementation.
...	...	@@ -67,13 +67,11 @@
67	67	== 5. Key takeaways ==
68	68
69	69	* The key aspects are:
70		- * H2 Database temporarily stores data
71		- * Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
72		- * Holds data in case the queue (the onramp) cannot be reached
73		- * Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
	65	+ ** H2 Database temporarily stores data
	66	+ ** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	67	+ ** Holds data in case the queue (the onramp) cannot be reached
	68	+ ** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
74	74
75		-
76		-
77	77	== 6. Suggested Additional Readings ==
78	78
79	79	If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
...	...	@@ -80,8 +80,7 @@
80	80
81	81	== 7. Silent demonstration video ==
82	82
83		-As this is a more theoretical microlearning we have no video for this
84		-)))
	76	+As this is a more theoretical microlearning we have no video for this)))
85	85
86	86	((({{toc/}}))){{/container}}
87	87	{{/container}}