Skip to Content

Changes for page Multi-Model Explained

Last modified by Erik Bakker on 2024/08/08 11:57
From version 9.1
edited by Carlijn Kokkeler
on 2022/10/14 09:59
Change comment: There is no comment for this version
To version 12.1
edited by Carlijn Kokkeler
on 2022/10/20 16:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,10 +9,10 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
12 -* An environment in eMagiz in which there are multiple integration models is called a multi-model environment.
12 +* An environment in eMagiz in which there are multiple integration models is called a multi-model environment.
13 13  * With integration model, an eMagiz platform instance is meant, in which it is possible to build integrations.
14 14  * 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.
15 -* 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.
15 +* 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.
16 16  
17 17  == 3. eMagiz multi-model environment - Definition ==
18 18  
... ... @@ -33,7 +33,7 @@
33 33  === 4.1 Independent operations ===
34 34  
35 35  Within a company, there may be different business processes that can operate independently. It can be useful to have a clear separation in these business processes, such that the processes can evolve independently. This may include entirely different business processes, such as sales and transport, but processes can also be separated based on different use cases or different positions within a business process. For example, one model might address the business processes down the value chain, while the other model addresses the business processes up the value chain.
36 -By having an eMagiz model for each distinct business process, it possible to release new integrations and make changes independently, so that the processes can evolve freely. For example, in case there is a different model for sales and transport, there is no dependency on progress of both departments. Below, it is illustrated that, in case a flow that is being worked on for the sales department is still in progress, while a flow that is being worked on for the transport department is done, no new release can be made if the models are not separated. In case there is a separate model for the sales department and the transport department, releases can be made independently, meaning that the improvement on the flow for the transport department can already be released.
36 +By having an eMagiz model for each distinct business process, it is possible to release new integrations and make changes independently, so that the processes can evolve freely. For example, in case there is a different model for sales and transport, there is no dependency on progress of both departments. Below, it is illustrated that, in case a flow that is being worked on for the sales department is still in progress, while a flow that is being worked on for the transport department is done, no new release can be made if the models are not separated. In case there is a separate model for the sales department and the transport department, releases can be made independently, meaning that the improvement on the flow for the transport department can already be released.
37 37  
38 38  
39 39  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-multi-model--independent-operations-single-instance.png]]