Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 7.2
edited by Danniar Firdausy
on 2024/09/11 20:45
Change comment: There is no comment for this version
To version 2.2
edited by Erik Bakker
on 2022/06/10 13:10
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Considering Dependencies between integrations
1 +intermediate-risk-management-considering-dependencies-between-integrations
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,13 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Considering Dependencies between integrations =
3 +
2 2  In this microlearning, we will learn what you should consider when looking at dependencies between integrations. An integration solution can consist of loads of different integrations, and several of those integrations can depend on each other. For example, when looking at an Order 2 Cash process in which an order travels from system A to B, and as a result, various messages are returned in sequence (i.e., conformation, shipment, invoice). Logic dictates that, for example, when the order never arrives, the other integrations will also not receive any data. Therefore it is relevant to consider these dependencies while performing a risk assessment.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: October 19th, 2021
9 +* Required reading time: 4 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Advanced knowledge of the eMagiz platform
... ... @@ -17,6 +17,8 @@
17 17  * Are there dependencies?
18 18  * Will the failure of integration block another?
19 19  
25 +
26 +
20 20  == 3. Considering Dependencies between integrations ==
21 21  
22 22  In this microlearning, we will learn what you should consider when looking at dependencies between integrations. An integration solution can consist of loads of different integrations, and several of those integrations can depend on each other. For example, when looking at an Order 2 Cash process in which an order travels from system A to B, and as a result, various messages are returned in sequence (i.e., conformation, shipment, invoice). Logic dictates that, for example, when the order never arrives, the other integrations will also not receive any data. Therefore it is relevant to consider these dependencies while performing a risk assessment.
... ... @@ -26,7 +26,7 @@
26 26  * Are there dependencies?
27 27  * Will the failure of integration block another?
28 28  
29 -At first, we need to consider whether there are dependencies or whether each integration can perform its job without being influenced by other integrations. In scenarios of no dependence, there is also no risk of dependencies creating a cascade of problems. However, in situations where there are dependencies, one action could impact other integrations. An excellent example in a messaging environment is asynchronous routing. All asynchronous data traffic is passing the asynchronous routing and therefore changes to the routing directly impact all asynchronous integrations. So considering how, if and when to deploy an asynchronous routing is something worth thinking about.
36 +At first, need to consider whether there are dependencies or whether each integration can perform its job without being influenced by other integrations. In scenarios of no dependence, there is also no risk of dependencies creating a cascade of problems. However, in situations where there are dependencies, one action could impact other integrations. An excellent example in a messaging environment is asynchronous routing. All asynchronous data traffic is passing the asynchronous routing and therefore changes to the routing directly impact all asynchronous integrations. So considering how, if and when to deploy an asynchronous routing is something worth thinking about.
30 30  
31 31  The same applies to when you deploy other parts of the solution that could impact different integrations. Always ask yourself whether the quality of the answer will be upheld by the action you are about to perform.
32 32  
... ... @@ -34,13 +34,25 @@
34 34  
35 35  Being aware of these dependencies can significantly improve the choices you and the business make in terms of risk mitigation before developing your solutions via the eMagiz platform.
36 36  
37 -== 4. Key takeaways ==
38 38  
45 +
46 +== 4. Assignment ==
47 +
48 +See if you can determine the dependencies within your model. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
49 +
50 +== 5. Key takeaways ==
51 +
39 39  * Dependencies are relevant when deploying and when running the model
40 40  * Failure in one integration can block other integrations (or reduce its value)
41 41  
42 -== 5. Suggested Additional Readings ==
43 43  
56 +
57 +== 6. Suggested Additional Readings ==
58 +
44 44  There are no suggested additional readings on this topic.
45 45  
61 +== 7. Silent demonstration video ==
62 +
63 +There is no video for this microlearning.
64 +
46 46  )))((({{toc/}}))){{/container}}{{/container}}