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

...	...	@@ -3,11 +3,8 @@
3	3	(((
4	4	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.
5	5
6		-Should you have any questions, please contact academy@emagiz.com.
	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,10 +21,10 @@
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	29
30	30
...	...	@@ -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
	35	+ ** H2 Database temporarily stores data
	36	+ ** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	37	+ ** Holds data in case the queue (the onramp) cannot be reached
	38	+ ** 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
...	...	@@ -67,10 +67,10 @@
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
	67	+ ** H2 Database temporarily stores data
	68	+ ** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	69	+ ** Holds data in case the queue (the onramp) cannot be reached
	70	+ ** 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	75
76	76