Last modified by Danniar Firdausy on 2023/08/11 10:54
From version 21.2
edited by eMagiz
on 2022/06/08 12:30
Change comment: Update document after refactoring.
To version 23.1
edited by eMagiz
on 2022/06/08 12:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -intermediate-discover-your-integration-landscape-determining-integration-pattern
1 +Determining Integration Pattern
Content
... ... @@ -85,8 +85,6 @@
85 85  
86 86  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.
87 87  
88 -===== Practice =====
89 -
90 90  == 4. Assignment ==
91 91  
92 92  Reflect on the choices made within various projects and see if you would change the specific implementation with what you know now.