Skip to Content

Changes for page Multi-Model Explained

Last modified by Erik Bakker on 2024/08/08 11:57
From version 15.1
edited by Erik Bakker
on 2023/01/23 13:35
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2022/10/20 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  == 3. eMagiz multi-model environment - Definition ==
18 18  
19 -For some companies that work with eMagiz, it is preferable to have multiple integration models. Such an environment in eMagiz, in which there are multiple integration models, is called a multi-model environment. With integration model, an eMagiz platform instance is meant, in which it is possible to build integrations. Within an integration model, three types of integration patterns can be modelled. These are [[Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction||target="blank"]], [[API Gateway>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction||target="blank"]], and [[Event Streaming>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]]. An illustration of an integration model, or platform instance, with the Messaging integration pattern is the following:
19 +For some companies that work with eMagiz, it is preferable to have multiple integration models. Such an environment in eMagiz, in which there are multiple integration models, is called a multi-model environment. With integration model, an eMagiz platform instance is meant, in which it is possible to build integrations. Within an integration model, three types of integration patterns can be modelled. These are [[Messaging>>doc:Main.eMagiz Academy.Fundamentals.fundamental-messaging-introduction.WebHome||target="blank"]], [[API Gateway>>doc:Main.eMagiz Academy.Fundamentals.fundamental-api-gateway-introduction.WebHome||target="blank"]], and [[Event Streaming>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction.WebHome||target="blank"]]. An illustration of an integration model, or platform instance, with the Messaging integration pattern is the following:
20 20  
21 21  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-multi-model--single-platform-instance.png]]
22 22  
... ... @@ -26,7 +26,7 @@
26 26  
27 27  Per integration model, it is possible to decide which integration patterns are available. This may be only one pattern, but it could also be two, or all three.
28 28  
29 -== 4. Separation of concerns ==
29 +== 4 Separation of concerns ==
30 30  
31 31  There are several reasons for choosing multiple integrations models, i.e. separate eMagiz instances. These reasons can be grouped under the term separation of concerns. Separation of concerns is a design principle in software development and architecture for separating an application in two or more sections, such that each section addresses a particular concern. Reasons for applying this separation of concerns principle in the eMagiz environment are given below.
32 32