Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 13:24
From version 25.1
edited by Erik Bakker
on 2022/08/23 09:39
Change comment: There is no comment for this version
To version 29.1
edited by Eva Torken
on 2023/12/07 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -16,9 +16,9 @@
16 16  The focal point of this microlearning will be to figure out how you can best decide between the various "first-class" integration patterns.
17 17  
18 18  * The key aspects are:
19 - * The three "first-class" patterns are messaging, event streaming, and API gateway
20 - * Each pattern has pros and cons
21 - * Decide which pattern suits best based on business and technical checks and balances
19 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
20 + ** Each pattern has pros and cons
21 + ** Decide which pattern suits best based on business and technical checks and balances
22 22  
23 23  == 3. Determining Integration Pattern ==
24 24  
... ... @@ -27,15 +27,15 @@
27 27  The focal point of this microlearning will be to figure out how you can best decide between the various "first-class" integration patterns.
28 28  
29 29  * The key aspects are:
30 - * The three "first-class" patterns are messaging, event streaming, and API gateway
31 - * Each pattern has pros and cons
32 - * Decide which pattern suits best based on business and technical checks and balances
30 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
31 + ** Each pattern has pros and cons
32 + ** Decide which pattern suits best based on business and technical checks and balances
33 33  
34 34  As stated above, there are three "first-class" integration patterns within eMagiz. Each of these patterns has a unique way of processing the data. In this microlearning, we will look at how to decide which pattern best fits your integration challenge. Before we do that, let us first quickly look at the three integration patterns. In the picture below, you see a visual representation of each of the three patterns.
35 35  
36 36  [[image:Main.Images.Microlearning.WebHome@intermediate-discover-your-integration-landscape-determining-integration-pattern--the-three-patterns-visualized.png]]
37 37  
38 -As you can see, each pattern works differently. If you want an in-depth introduction to messaging, please check out this [microlearning](crashcourse-messaging-introduction.md). If you want an in-depth introduction to event streaming, please check out this [microlearning](crashcourse-eventstreaming-event-streaming-introduction.md). If you want an in-depth introduction to API gateway, please check out this [microlearning](crashcourse-api-gateway-introduction.md).
38 +As you can see, each pattern works differently. If you want an in-depth introduction to messaging, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-introduction||target="blank"]]. If you want an in-depth introduction to event streaming, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-event-streaming-introduction||target="blank"]]. If you want an in-depth introduction to API gateway, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-introduction||target="blank"]].
39 39  
40 40  Because each pattern works differently, each pattern has its pros and its cons. Depending on your specific use case, the balance between the pros and cons of one of the patterns will favor the pros. As a result, you should choose that option. But then, you ask, on what grounds should I make the decision? The answer is a series of checks and balances that look both at the business and technical aspects.
41 41  
... ... @@ -80,24 +80,18 @@
80 80  
81 81  So that means that you might save money in the short with sticking what you know but could end up paying more due to (significantly) higher implementation costs. Another piece of the puzzle is the resource costs. For this aspect also the resource costs differ per integration pattern. Here we see that taking a messaging solution would incur the highest resource costs. API Gateway and Event Streaming roughly take up the same amount of resource costs. We want to note that a large portion of the resource costs for Event Streaming lies in storage. So when you can reduce that component, the Event Streaming option would become even more cost-friendly. Hopefully, this microlearning will help you to make the correct decision per integration question.
82 82  
83 -== 4. Assignment ==
83 +== 4. Key takeaways ==
84 84  
85 -Reflect on the choices made within various projects and see if you would change the specific implementation with what you know now.
86 -
87 -== 5. Key takeaways ==
88 -
89 89  * The key aspects are:
90 - * The three "first-class" patterns are messaging, event streaming, and API gateway
91 - * Each pattern has pros and cons
92 - * Decide which pattern suits best based on business and technical checks and balances
86 + ** The three "first-class" patterns are messaging, event streaming, and API gateway
87 + ** Each pattern has pros and cons
88 + ** Decide which pattern suits best based on business and technical checks and balances
93 93  
94 -== 6. Suggested Additional Readings ==
90 +== 5. Suggested Additional Readings ==
95 95  
96 96  If you are interested in this topic, please get in touch with academy@emagiz.com.
97 97  
98 -== 7. Silent demonstration video ==
94 +)))
99 99  
100 -As this is a more theoretical microlearning, we have no video for this.)))
101 -
102 102  ((({{toc/}}))){{/container}}
103 103  {{/container}}