Changes for page Impact of changing topic retention

Summary

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

Details

Page properties

Content

...	...	@@ -25,23 +25,23 @@
25	25
26	26	=== 3.2 Does the size in Design Architecture consider the segment size? ===
27	27
28		-The total size in eMagiz that is displayed in the Design phase * Architecture takes into account the complex calculations around segment sizing, cleanup policies etc. So your sizing can never exceed that value on our Event Streaming cluster. eMagiz uses this value to determine the required licensing.
	28	+The total size in eMagiz that is displayed in the Design phase * Architecture takes into account the complex calculations around segment sizing, cleanup policies etc. So your sizing can never exceeed that value on our Event Streaming cluster. eMagiz uses this value to determine the required licensing.
29	29
30	30	=== 3.3 Actual retention vs. budget retention ===
31	31
32		-Despite the fact that you set a retention hours setting, it may occur that the amount of messages is so large that the retention bytes kicks in earlier than the retention hours. This could cause an effect that the oldest messages is younger than your retention hour setting. In specific scenario's this can be an issue.
	32	+Despite the fact that you set a retention hours setting, it may occur that the amount of messages is so large that the retention bytes kicks in earlier than the retention hours. This could cause an effect that the oldest messages is younger than your retention hour setting. In specific scenario's this can be an issues
33	33
34	34	=== 3.4 Managing retention across TAP ===
35	35
36		-You are able to set the retention bytes and hours per Test, Acceptance and Production. You can play with these configuration values by setting a smaller value for Test compared to Production. So that each topic is optimized for the environment at hand. One advice can be to keep Acceptance and Production similar in terms of configuration for retention whereas Test can be set to a lower value.
	36	+You are able to set the retention bytes and hours per Test, Acceptance and Production. You can play with this configuration values by setting a smaller value for Test compared to Production. So that each topic is optimized for the environment at hand. One advice can be to keep Acceptance and Production similar in terms of configuration for retention * test can be set to a lower value.
37	37
38		-{{info}}During development of a new business process that involves the use of topics, only test can be given sufficient retention values. In this case, Acceptance and Production topics can be disabled so that the total licensed size is not exceeded.{{/info}}
	38	+During development of a new business process that involves the use of topics, only test can be given sufficient retention values. In this case, Acceptance and Production topics can be disabled so that the total licensed size is not exceeded.
39	39
40	40	=== 3.5 Duplication of data ===
41	41
42		-* At this moment the standard setting for the number of partitions is 1. In case you change this value to 10 and keep your retention bytes at the same level, you will have a reserved data storage that is 10 times larger as before. As a consequence you might run out of allotted size to fast for your own comfort.
	42	+* At this moment the standard setting for the number of partitions is 1. In case you change this value to 10, then you will have a reserved data storage of 10 times the retention bytes. The grand effect might be that the when adding all topics together including the segment size could increase the total size substantially.
43	43
44		-* When designing solutions in eMagiz using Event Streaming, make sure to make the right decision on the storage of intermediate results. You could store an intermediate result of a process step in a next topic that then in turn feeds the next step in the business process. In this case, it might be that the use of too many topics for the same business process causes an exponential increase of data storage. Try to make a sound decision in this by combining steps or by looking at alternatives.
	44	+* When design solutions in eMagiz using Event Streaming, then make sure to make the right decision on the storage of intermediate results. You could store a intermediate result of a process step in a next topic that then in turn takes the next step in the business process. In this case, it might be that the use of too many topics for the same business process causes an exponential increase of data storage. Try to make a sound decision in this by combining steps or alternative.
45	45
46	46	== 4. Assignment ==
47	47