Last modified by Danniar Firdausy on 2024/09/18 21:32
From version 8.2
edited by Danniar Firdausy
on 2024/09/11 20:52
Change comment: There is no comment for this version
To version 9.2
edited by Danniar Firdausy
on 2024/09/18 21:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
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.
2 +In this microlearning, we will explore how to assess dependencies between integrations. When dealing with complex integration solutions, it's crucial to understand how various components interact with each other. For example, in an Order 2 Cash process, the failure of an order to arrive could impact the subsequent messages like confirmation, shipment, and invoice. We'll discuss how to identify these dependencies, evaluate their impact, and ensure that your integration solution remains robust and efficient.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,8 +9,8 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
12 -This microlearning centers around considering dependencies between integration
13 -With dependencies, we mean: The matter in which the outcome of another integration dictates the working of one integration
12 +This microlearning centers around considering dependencies between integration.
13 +* With dependencies, we mean: The matter in which the outcome of another integration dictates the working of one integration
14 14  
15 15  When looking at dependencies, we ought to consider:
16 16  
... ... @@ -36,12 +36,15 @@
36 36  
37 37  == 4. Key takeaways ==
38 38  
39 -* Dependencies are relevant when deploying and when running the model
40 -* Failure in one integration can block other integrations (or reduce its value)
39 +* Understand how different integrations are interconnected and how one integration's outcome can affect others.
40 +* Evaluate whether the failure of one integration might block or disrupt other integrations within the process.
41 +* Implement strategies to manage and minimize risks related to integration dependencies, both during deployment and in ongoing operations.
42 +* Ensure that integration solutions are designed to handle dependencies effectively, maintaining functionality and value even when issues arise.
41 41  
42 42  == 5. Suggested Additional Readings ==
43 43  
44 44  If you are interested in this topic and want more information, please check out these links:
47 +
45 45  * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
46 46  ** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
47 47  *** [[Asynchronous Routing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-routing]]