Skip to Content

Changes for page eMagiz Store

Last modified by Erik Bakker on 2024/08/26 11:02
From version 16.1
edited by eMagiz
on 2022/06/13 09:34
Change comment: There is no comment for this version
To version 17.1
edited by Erik Bakker
on 2022/06/13 12:37
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,7 +1,4 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -<div class="doc">
1 +{{container}}{{container layoutStyle="columns"}}(((
5 5  
6 6  
7 7  
... ... @@ -11,9 +11,6 @@
11 11  
12 12  Should you have any questions, please get in touch with academy@emagiz.com.
13 13  
14 -* Last update: November 4th, 2021
15 -* Required reading time: 6 minutes
16 -
17 17  == 1. Prerequisites ==
18 18  
19 19  * Some context on cloud functionality will be helpful.
... ... @@ -40,7 +40,7 @@
40 40  
41 41  The first perspective on the Cloud we take is how we run multiple customers within the same eMagiz Cloud solution that we offer. The picture below shows how we structured our Cloud to ensure that your data is kept safely within your environment.
42 42  
43 -<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--high-overview.png||]]</p>
37 +[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--high-overview.png]]
44 44  
45 45  The most outer line of the picture represents the total eMagiz Cloud. Our support department and cloud admins have access to this level from which they can access each customer environment if need be. When going one level deeper, we see the standard region in which all our customers' data is kept. This default region (eu-central-01 located in Frankfurt) allows us to keep data under European Law and reduces the latency as most of our customer base is located within the European continent. Within this region, we have what we call a Carwash. This carwash is placed in front of each of our customer VPC's to add a layer of security. This layer restricts access to customer endpoints. Behind the carwash, we have one separate VPC per customer model. So when you have multiple models running in eMagiz (as part of your Enterprise license), you will effectively have the same amount of VPCs in the Cloud (assuming all of them run in the Cloud). This allows for the best possible separation of concerns between customers and models.
46 46  
... ... @@ -48,7 +48,7 @@
48 48  
49 49  Now that we have a conceptual idea of how the various customers within the Cloud are separated from each other, we will zoom in on how a standard single-lane VPC setup looks.
50 50  
51 -<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--customer-level-overview.png||]]</p>
45 +[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview.png]]
52 52  
53 53  We once again see the outer layers of the eMagiz Cloud and the region. But in this overview, we zoomed in on one of the customer VPCs we have shown in the previous paragraph. When zooming in, we see several new things emerge within the picture. At first, we have an Internet Gateway that connects your VPC to the internet. This way, the carwash can redirect the traffic to the correct VPC, and the VPC is subsequently able to receive and process the message. Immediately after the gateway, we have a load balancer that determines whether the data is on HTTPS or JMS level. Depending on that, the message will be either sent to the core or the connector machine. This allows each VPC to communicate securely with the outside world and means that HTTPS traffic cannot be sent to the core machine.
54 54  
... ... @@ -68,7 +68,7 @@
68 68  
69 69  In the previous overview, we showed a single-lane setup. In the outline below, we deliver what we call a double lane setup. The most fundamental difference between the two is that you have a mirror image of each piece of functionality you are running with the double lane. Having a mirror image of everything reduces the downtime of the environment during maintenance and unexpected outings of your environment.
70 70  
71 -<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png||]]</p>
65 +[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png]]
72 72  
73 73  In this double lane setup, the backup JMS is dormant until activated. All processing components running in the Cloud will run at the same. As a result, you will see the number of consumers double across all your queues.
74 74  
... ... @@ -84,8 +84,8 @@
84 84  * A carwash is placed in front of all VPCs to add a layer of security
85 85  * You can add additional features to your specific VPC
86 86  
87 -===== Practice =====
88 88  
82 +
89 89  == 4. Key takeaways ==
90 90  
91 91  * Each eMagiz model result in a separate VPC in the eMagiz Cloud
... ... @@ -107,8 +107,4 @@
107 107  * [Intermediate - eMagiz Cloud Management](../microlearning/intermediate-emagiz-cloud-management-index.md)
108 108  * [Advanced - eMagiz Cloud Management](../microlearning/advanced-cloudmanagement-index.md)
109 109  
110 -</div>
111 -</div>
112 -</div>
113 -
114 -{{/html}}
104 +)))((({{toc/}}))){{/container}}{{/container}}