Skip to Content

Changes for page Retention Policy

Last modified by Danniar Firdausy on 2024/09/18 15:56
From version 4.1
edited by Erik Bakker
on 2022/08/30 12:25
Change comment: There is no comment for this version
To version 6.1
edited by Eva Torken
on 2023/08/25 15:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -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.WebHome||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.WebHome||target="blank"]].
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"]].
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,12 +37,8 @@
37 37  
38 38  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.
39 39  
40 -== 4. Assignment ==
40 +== 4. Key takeaways ==
41 41  
42 -Check out if you have a project in which the Event Streaming pattern is used. If so, check out the retention policy for several topics.
43 -
44 -== 5. Key takeaways ==
45 -
46 46  * The key aspects are:
47 47   ** Retention Hours
48 48   ** Retention Bytes
... ... @@ -49,12 +49,7 @@
49 49   ** Cleanup Policy
50 50   ** These three items determine the retention policy
51 51  
52 -== 6. Suggested Additional Readings ==
48 +== 5. Suggested Additional Readings ==
53 53  
54 54  If you are interested in this topic, please read the help text eMagiz provides you.
55 -
56 -== 7. Silent demonstration video ==
57 -
58 -As this is a more theoretical microlearning, we have no video for this.
59 -
60 60  )))((({{toc/}}))){{/container}}{{/container}}