Changes for page Retention Policy

Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In this microlearning, we will dive a little bit deeper into the concept of the retention policy concerning Event Streaming. Retention policy determines when a message needs to be cleaned up and, if so, what will happen to the message.
	2	+In this microlearning, we will explore how retention policies manage the lifecycle of messages in your streaming system. Specifically, we will focus on the factors that influence when messages are cleaned up and the actions taken when this occurs.
3	3
4	4	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
...	...	@@ -11,12 +11,6 @@
11	11
12	12	This microlearning centers on the retention policy for Event Streaming.
13	13
14		-* The key aspects are:
15		- ** Retention Hours
16		- ** Retention Bytes
17		- ** Cleanup Policy
18		- ** These three items determine the retention policy
19		-
20	20	== 3. Event Streaming ==
21	21
22	22	In this microlearning, we will dive a little bit deeper into the concept of the retention policy concerning Event Streaming. Retention policy determines when a message needs to be cleaned up and, if so, what will happen to the message.
...	...	@@ -27,7 +27,7 @@
27	27	** Cleanup Policy
28	28	** These three items determine the retention policy
29	29
30		-As we learned in the introductory [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]], the topic holds a log with a sequence of messages. Based on several criteria, the broker decides when to remove messages from the back of the log to ensure that the topic stays within specific parameters. These parameters are the retention hours and the retention bytes. If you want to learn more about them specifically, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-topic-and-topic-properties||target="blank"]].
	24	+As we learned in the [[introductory microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]], the topic holds a log with a sequence of messages. Based on several criteria, the broker decides when to remove messages from the back of the log to ensure that the topic stays within specific parameters. These parameters are the retention hours and the retention bytes. If you want to learn more about them specifically, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-topic-and-topic-properties||target="blank"]].
31	31
32	32	These parameters combined with the cleanup policy determine what happens with a message after it is expired. There are two options available:
33	33	* delete
...	...	@@ -37,19 +37,18 @@
37	37
38	38	{{info}}The cleanup policy <compact> is not used in eMagiz.{{/info}}
39	39
40		-The three aspects combine to make up the retention policy. Defining the correct values for both the retention hours and the retention bytes is a science as a form of art. As you only have limited storage capacity available, the challenge becomes how much retention you reserve per topic. The more you assign, the less free storage capacity remains for other topics. As a consequence, you need to strive to optimize your retention policy per topic continually.
	34	+These three aspects above combine to make up the retention policy. Defining the correct values for both the retention hours and the retention bytes is a science as a form of art. As you only have limited storage capacity available, the challenge becomes how much retention you reserve per topic. The more you assign, the less free storage capacity remains for other topics. As a consequence, you need to strive to optimize your retention policy per topic continually.
41	41
42	42	== 4. Key takeaways ==
43	43
44		-* The key aspects are:
45		- ** Retention Hours
46		- ** Retention Bytes
47		- ** Cleanup Policy
48		- ** These three items determine the retention policy
	38	+* Retention Hours: Defines how long messages are kept before they are eligible for cleanup.
	39	+* Retention Bytes: Specifies the maximum amount of storage space allocated for messages before older ones are removed.
	40	+* Cleanup Policy: Determines the method of message removal once the retention criteria are met. The default policy is to delete expired messages, though an alternative, compact, is not used in eMagiz.
49	49
50	50	== 5. Suggested Additional Readings ==
51	51
52	52	If you are interested in this topic and want more information on it, please read the help text provided by eMagiz when executing these actions and browse through the following links:
	45	+
53	53	* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
54	54	** [[Crash Course Event Streaming (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.WebHome||target="blank"]]
55	55	*** [[Event Streaming - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]]