Changes for page Considering impact of downtime
Last modified by Erik Bakker on 2024/09/03 08:54
To version 4.1
edited by Erik Bakker
on 2022/10/03 13:54
on 2022/10/03 13:54
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,0 +1,1 @@ 1 +Considering Impact of Downtime - Parent
-
... ... @@ -1,0 +1,1 @@ 1 +WebHome - Default language
-
... ... @@ -1,0 +1,1 @@ 1 +en - Content
-
... ... @@ -1,13 +1,8 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -= Considering Impact of Downtime = 3 - 4 4 In this microlearning, we will learn what you should consider determining the impact of downtime on the business. We will consider the impact when some specific part of the integration solution experiences downtime. From there on, we broaden our view to determine when multiple parts or even the whole integration solution experiences downtime. What should not be forgotten is the potential impact when the entire integration solution is running, but specific target systems are unreachable. It would be best to discuss what to do when it happens and mitigate the risks involved in all these scenarios. 5 5 6 6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 7 7 8 -* Last update: October 19th, 2021 9 -* Required reading time: 6 minutes 10 - 11 11 == 1. Prerequisites == 12 12 13 13 * Advanced knowledge of the eMagiz platform ... ... @@ -24,8 +24,6 @@ 24 24 * What is the complete integration solution is down? 25 25 * What if a target system is down and therefore unreachable? 26 26 27 - 28 - 29 29 == 3. Considering Impact of Downtime == 30 30 31 31 In this microlearning, we will learn what you should consider determining the impact of downtime on the business. We will consider the impact when some specific part of the integration solution experiences downtime. From there on, we broaden our view to determine when multiple parts or even the whole integration solution experiences downtime. What should not be forgotten is the potential impact when the entire integration solution is running, but specific target systems are unreachable. It would be best to discuss what to do when it happens and mitigate the risks involved in all these scenarios. ... ... @@ -76,8 +76,6 @@ 76 76 * Discuss potential risks and appropriate actions beforehand with the customer 77 77 * Use the most suitable integration pattern for the needs of the customer 78 78 79 - 80 - 81 81 == 4. Assignment == 82 82 83 83 See if you can determine the impact of downtime and assign risk-mitigating rules to this impact. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment. ... ... @@ -89,8 +89,6 @@ 89 89 * eMagiz offers several mitigations out of the box 90 90 * You should consider which additional measures need to be taken 91 91 92 - 93 - 94 94 == 6. Suggested Additional Readings == 95 95 96 96 There are no suggested additional readings on this topic.