Changes for page eMagiz Store

Summary

• Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-eMagiz Store
	1	+eMagiz Cloud - Inner Workings

Parent

...	...	@@ -1,1 +1,1 @@
1		-Main.eMagiz Academy.Fundamentals.WebHome
	1	+WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,5 +1,5 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In this fundamental, we will zoom in on the concepts of the eMagiz Store and how it can benefit our community whilst developing within the platform. Building on this fundamental we have several [[microlearnings>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]] related to the eMagiz Store that give a more in-depth explanation on the technicalities when working with the store.
	2	+In this fundamental, we will zoom in on how the eMagiz Cloud is structured and how it functions for you as a customer. We will start our journey at a high level in which we focus on how we support multiple customer environments within the same eMagiz Cloud. From there, we will in on the details of each of those customer environments. Building on that, we show the differences between a single lane and a double lane setup. Last but not least, we will focus on the key benefits deploying in the eMagiz Cloud holds for you.
3	3
4	4	Should you have any questions, please get in touch with academy@emagiz.com.
5	5
...	...	@@ -9,34 +9,56 @@
9	9
10	10	== 2. Key concepts ==
11	11
12		-* The eMagiz Store is accessible from various phases of the ILM
13		-* The eMagiz Store is designed for reusability, speed, and transfering best-practices
14		-* Generic content is maintained by eMagiz. Partners content is maintained by our partners.
15		-* The eMagiz content is divised into connectors and accelerators
	12	+* Each eMagiz model is deployed in a client specific VPC (Virtual Private Cloud) in the eMagiz Cloud
	13	+* The eMagiz Cloud is automated on AWS technology - all VPC's reside in eu-central-01
	14	+* A carwash serves as entry point for all incoming traffio to allow highest level of security and to route this traffice to the right VPC
	15	+* Each VPC has DNS functionality to ensure that external systems don't have to call an IP address directly
	16	+* Each VPC is automatically monitored by the eMagiz Cloud
	17	+* You can add additional features to your specific VPC such as DirectConnect, VPN or fixed IP addresses
	18	+* A double lane means that all machines are duplicated to increase uptime of the deployed Model. The JMS Server is setup in a failover (active-passive) manner
16	16
17		-== 3. eMagiz Store ==
	20	+== 3. eMagiz Cloud - Inner Workings ==
18	18
19		-We have designed the eMagiz Store in such a way that it supports our users whilst developing in the Design and Create phase of eMagiz in creating a working integration. Store items developed by eMagiz and by our partners focus on increasing the speed of delivery, promoting reusability across models and instilling best-practices in the hearts and minds of our users.
	22	+When running your eMagiz solution, there are generally two methods of deploying. There is the Cloud and the on-premise (i.e., in your own data center) option. We see a strong development towards Cloud-based functionality across markets. Furthermore, we see that patterns such as API Gateway and Event Streaming are tailored for a cloud only approach. Given all those characteristics, we have an eMagiz Cloud first strategy when further developing our patterns and features across the platform.
20	20
21		-The eMagiz Store currently plays host to a large number of connectors connecting to systems such as Exact Online, Salesforce, SAP, Microsoft Graph and more. On top of that we offer a wide range of accelerators that contain often used transformations, standardized connectivity methods (i.e. REST, SOAP, SFTP) and technically challenging solution that could come in handy (i.e. Groovy solutions).
	24	+In this fundamental, we will zoom in on how the eMagiz Cloud is structured and how it operates for you as a customer. We will start our journey at a high level in which we focus on how we support multiple customer environments within the same eMagiz Cloud. From there, we will in on the details of each of those customer environments. Building on that, we show the differences between a single lane and a double lane setup. Last but not least, we will focus on the key benefits deploying in the eMagiz Cloud holds for you.
22	22
	26	+=== 3.1 High-level overview ===
23	23
	28	+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.
24	24
25		-=== 3.1 Content Management ===
	30	+[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--high-overview.png]]
26	26
27		-Within the eMagiz store we have two streams of content that can be publiced in the store. The first stream of content is maintained and managed by ourselves as eMagiz. This stream focuses on accelerators (i.e. store items that simplify something in Create such as calling a REST endpoint) and on generic connectors (i.e. connectors that are used in a wide variety of markets, such as Salesforce). The secondary stream of content is maintained and managed by each of our partners. As partner they have the option to export relevant content for their own customer base to the eMagiz store to further enhance the experience in using the platform and adding value faster.
	32	+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.
28	28
29		-=== 3.2 Suggestions, Questions and Feedback ===
	34	+=== 3.2 Customer level overview ===
30	30
31		-We can imagine that when using the store or simply browsing through what the store can offer you suggestions, questions and feedback might arise. In each of these cases we appreciate you contact us in a specific manner. In case you have suggestions for new feedback do not hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]]. In case of questions please use our Q&A forum within the portal. In case of feedback you can use the feedback button in the portal to report your feedback so we can take a look at it.
	36	+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.
32	32
33		-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.
	38	+[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview.png]]
34	34
35		-=== 3.3 Example usage ===
	40	+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.
36	36
37		-Within the documentation portal we have a list of connectors and accelerators that are managed and maintained by eMagiz. The list can be found [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]]. On top of that we have some example videos in which we demonstrate how you can use the store to your advantage through the use of some use cases. Please check out the links below for each of these use cases:
	42	+Below the load balancer, we show our DNS functionality. This ensures that when external parties call an endpoint hosted within one of your flows, they do not have to know the IP address of your VPC but can call the DNS name that you configured partly within the portal. We finished off by replacing the IP with emagizcloud.com within all the endpoints that are hosted by eMagiz. This makes life way easier when allowing external parties to connect to your endpoints.
38	38
	44	+At the bottom of the picture, we see the EFS (Elastic File System). This file storage system stores meta-information securely for each customer so that only that customer can access it. A benefit of using this solution instead of regular file storage is that it can automatically scale. As a result, our cloud offering becomes more robust in dealing with high surges of traffic. Furthermore, by using EFS, your data is kept separate from the machines and can be re-used if the machines within the VPC need to be spun up in a different availability zone. To review: The EFS is also located on multiple availability zones for redundancy and distaster recovery.
39	39
	46	+More to the right of the picture, we see the monitoring capabilities on the eMagiz Cloud level. Here we depict our most noteworthy monitoring functionality that will be triggered when your VPC or part of your VPC runs into trouble. Apart from the trigger, we also keep the log information for 30 days for analysis purposes if an RCA needs to be performed by eMagiz Support. This information is stored within the Systems Manager and CloudWatch.
	47	+
	48	+Some of the monitoring triggers lead to an auto-healing action that will restore the state of your environment to normal without anyone having to take action. This means that the downtime in case of an outage is significantly reduced in these cases.
	49	+
	50	+Moving over to the last portion of the overview, we see some of the features we offer on the eMagiz Cloud. For example, you can define a fixed IP on outbound traffic for cases where the external party uses IP whitelisting to verify traffic. Another feature is the data sink capability that stores sunk messages in a bucket to be retrieved from the portal.
	51	+
	52	+Please check out the suggested additional readings section for applied knowledge on how you can control the eMagiz Cloud from the portal and utilize some of these functionalities from the eMagiz portal.
	53	+
	54	+=== 3.3 Single lane vs. Double Lane ===
	55	+
	56	+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.
	57	+
	58	+[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png]]
	59	+
	60	+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.
	61	+
40	40	=== 3.4 Key benefits ===
41	41
42	42	Now that we have explained how our Cloud is configured, we will wrap up this fundamental by looking at the key benefits the Cloud holds for you when building your models with the help of the eMagiz platform. Below we have summarized these key benefits:
...	...	@@ -51,15 +51,21 @@
51	51
52	52	== 4. Key takeaways ==
53	53
54		-* The eMagiz Store is accessible from various phases of the ILM
55		-* The eMagiz Store is designed for reusability, speed, and transfering best-practices
56		-* Generic content is maintained by eMagiz. Partners content is maintained by our partners.
57		-* The eMagiz content is divised into connectors and accelerators
	76	+* Each eMagiz model result in a separate VPC in the eMagiz Cloud
	77	+* eMagiz models are deployed in the AWS eu-central-01 zone by default - other regions are possible upon request
	78	+* A carwash is placed in front of all VPCs to add a layer of security
	79	+* Each VPC has DNS functionality to ensure that external parties don't have to call an IP address directly
	80	+* Each VPC is automatically monitored
	81	+* You can add additional features to your specific VPC
	82	+* Setting up a double lane is a safeguard against downtime
	83	+* The eMagiz Cloud can be controlled via the eMagiz platform (check out our microlearnings under suggested additional readings)
58	58
59	59	== 5. Suggested Additional Readings ==
60	60
61		-If you are interested in this topic and want to learn how you can utilize the eMagiz Store whilst developing in the eMagiz platform, please check out our microlearnings offering on the eMagiz Store:
	87	+If you are interested in this topic and want to learn how you can control your Cloud with the help of the eMagiz platform, please check out our microlearnings offering on eMagiz Cloud Management:
62	62
63		-* [[Novice - eMagiz Store>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]
	89	+* [[Novice - eMagiz Cloud Management>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]]
	90	+* [[Intermediate - eMagiz Cloud Management>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]]
	91	+* [[Advanced - eMagiz Cloud Management>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.eMagiz Cloud Management.WebHome||target="blank"]]
64	64
65	65	)))((({{toc/}}))){{/container}}{{/container}}