Skip to Content

Changes for page Retention Policy

Last modified by Danniar Firdausy on 2024/09/18 15:56
From version 3.1
edited by eMagiz
on 2022/06/10 11: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.eMagiz
1 +XWiki.etorken
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,12 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -
3 3  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.
4 4  
5 5  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
7 -* Last update: August 4th, 2021
8 -* Required reading time: 4 minutes
9 -
10 10  == 1. Prerequisites ==
11 11  
12 12  * Intermediate knowledge of the eMagiz platform
... ... @@ -16,54 +16,40 @@
16 16  This microlearning centers on the retention policy for Event Streaming.
17 17  
18 18  * The key aspects are:
19 - * Retention Hours
20 - * Retention Bytes
21 - * Cleanup Policy
22 - * These three items determine the retention policy
15 + ** Retention Hours
16 + ** Retention Bytes
17 + ** Cleanup Policy
18 + ** These three items determine the retention policy
23 23  
24 -
25 -
26 26  == 3. Event Streaming ==
27 27  
28 28  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.
29 29  
30 30  * The key aspects are:
31 - * Retention Hours
32 - * Retention Bytes
33 - * Cleanup Policy
34 - * These three items determine the retention policy
25 + ** Retention Hours
26 + ** Retention Bytes
27 + ** Cleanup Policy
28 + ** These three items determine the retention policy
35 35  
36 -As we learned in the introductory [microlearning](crashcourse-eventstreaming-event-streaming-introduction.md), 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](crashcourse-eventstreaming-topic-and-topic-properties.md).
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"]].
37 37  
38 38  These parameters combined with the cleanup policy determine what happens with a message after it is expired. There are two options available:
39 -delete
40 -compact
33 +* delete
34 +* compact
35 +
41 41  The delete option is the default that eMagiz uses and advises. This option will, as the name suggests, delete all messages that are expired. There is an alternative approach called compact. This functionality will enable log compaction on the topic.
42 42  
43 43  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.
44 44  
40 +== 4. Key takeaways ==
45 45  
46 -
47 -== 4. Assignment ==
48 -
49 -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.
50 -
51 -== 5. Key takeaways ==
52 -
53 53  * The key aspects are:
54 - * Retention Hours
55 - * Retention Bytes
56 - * Cleanup Policy
57 - * These three items determine the retention policy
43 + ** Retention Hours
44 + ** Retention Bytes
45 + ** Cleanup Policy
46 + ** These three items determine the retention policy
58 58  
48 +== 5. Suggested Additional Readings ==
59 59  
60 -
61 -== 6. Suggested Additional Readings ==
62 -
63 63  If you are interested in this topic, please read the help text eMagiz provides you.
64 -
65 -== 7. Silent demonstration video ==
66 -
67 -As this is a more theoretical microlearning, we have no video for this.
68 -
69 69  )))((({{toc/}}))){{/container}}{{/container}}