Changes for page Retention Policy

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,9 +1,16 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
	1	+{{html wiki="true"}}
	2	+<div class="ez-academy">
	3	+ <div class="ez-academy_body">
	4	+
	5	+<div class="doc">
	6	+
	7	+
	8	+
2	2	= Retention Policy =
3	3
4	4	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.
5	5
6		-Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	13	+Should you have any questions, please get in touch with academy@emagiz.com.
7	7
8	8	* Last update: August 4th, 2021
9	9	* Required reading time: 4 minutes
...	...	@@ -43,8 +43,8 @@
43	43
44	44	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.
45	45
	53	+===== Practice =====
46	46
47		-
48	48	== 4. Assignment ==
49	49
50	50	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.
...	...	@@ -67,4 +67,9 @@
67	67
68	68	As this is a more theoretical microlearning, we have no video for this.
69	69
70		-)))((({{toc/}}))){{/container}}{{/container}}
	77	+</div>
	78	+
	79	+</div>
	80	+</div>
	81	+
	82	+{{/html}}