Changes for page H2 Database, Function

Summary

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

Details

Page properties

Content

...	...	@@ -1,6 +1,8 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
	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>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-h2-database-for-other-applications||target="blank"]] of the H2 database.
	5	+
4	4	When you create a new entry in eMagiz, you might notice that the H2 database component is automatically included. This can sometimes lead to confusion about its role and purpose. In this microlearning, we will clarify what the H2 database does and why it's an essential part of every new entry. We will break down its functions, including how it temporarily stores data, acts as a bridge between the entry and the queue, and helps manage data flow. Stick with us to get a clear understanding of this component and its importance in ensuring smooth and reliable message delivery.
5	5
6	6	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
...	...	@@ -25,6 +25,14 @@
25	25
26	26	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>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-h2-database-for-other-applications||target="blank"]] of the H2 database.
27	27
	30	+The focal point of this microlearning will be to figure out why the H2 database is part of any auto-generated entry.
	31	+
	32	+* The key aspects are:
	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
	37	+
28	28	As you probably noticed by now is that every time you create a new entry in eMagiz some components are automatically generated for you.
29	29
30	30	[[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-function-of-h2-database--auto-generation-entry.png]]
...	...	@@ -47,11 +47,11 @@
47	47
48	48	== 4. Key takeaways ==
49	49
50		-* The H2 Database temporarily stores incoming data to ensure it is not lost if there are issues with the connection to the queue (the onramp).
51		-* The H2 Database acts as an intermediary between the entry point where data arrives and the first queue, facilitating smooth data transfer.
52		-* In case the queue cannot be reached, the H2 Database holds the data until the connection is restored, ensuring no data is lost.
53		-* By periodically checking for new data, the H2 Database helps to regulate the flow of data from the connector to the container runtime, preventing overload and maintaining system performance.
54		-* The component aids in managing message throughput to avoid overwhelming the queue, contributing to efficient and reliable message processing.
	60	+* The key aspects are:
	61	+** H2 Database temporarily stores data
	62	+** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
	63	+** Holds data in case the queue (the onramp) cannot be reached
	64	+** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
55	55
56	56	== 5. Suggested Additional Readings ==
57	57