Changes for page H2 Database, Function

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -25,7 +25,7 @@
25	25
26	26	== 3. H2 Database, Function ==
27	27
28		-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.WebHome||target="blank"]] of the H2 database.
	28	+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.
29	29
30	30	The focal point of this microlearning will be to figure out why the H2 database is part of any auto-generated entry.
31	31
...	...	@@ -53,14 +53,10 @@
53	53
54	54	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).
55	55
56		-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
	56	+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 delivering messages.
57	57
58		-== 4. Assignment ==
	58	+== 4. Key takeaways ==
59	59
60		-Reflect on the choices made within various projects and see if you would, with what you know now, change the specific implementation.
61		-
62		-== 5. Key takeaways ==
63		-
64	64	* The key aspects are:
65	65	** H2 Database temporarily stores data
66	66	** Acts as a bridge between the entry (where data arrives or is retrieved) and the first queue (the onramp)
...	...	@@ -67,13 +67,10 @@
67	67	** Holds data in case the queue (the onramp) cannot be reached
68	68	** Smoothen the amount of data that is transported from the connector to the container runtime as it periodically checks for new data
69	69
70		-== 6. Suggested Additional Readings ==
	66	+== 5. Suggested Additional Readings ==
71	71
72	72	If you are interested in this topic and want more information on it please read the help texts provided by eMagiz
	69	+)))
73	73
74		-== 7. Silent demonstration video ==
75		-
76		-As this is a more theoretical microlearning we have no video for this)))
77		-
78	78	((({{toc/}}))){{/container}}
79	79	{{/container}}