Search: "deploy architecture"

Key differences Design & Deploy Architecture

In case a system is added to a Cloud Connector machine for instance, the Deploy architecture will allows to actually deploy that runtime. == 3.

However, in some cases the Deploy architecture looks different compared to the Design architecture.

These systems are not displayed in Deploy Architecture. [[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-diffs-design-deploy-2.png]] * Systems accessed via Exit Gates only Applications that accessed via API Gateway operations only are also no displayed in the Deploy Architecture.

Key concepts == With cloud template, we mean: A Cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting, for instance) are available for your environment.

All changes can be handled with a single push of a button, but it may become harder to isolate the root cause when an issue occurs. So keep your Deploy Architecture as current as possible.{{/info}} * Duration of the upgrade ** A Cloud template upgrade will take between 5 and 15 minutes, depending on the size of the slot in terms of machines.

Regardless of the type of environment (Test, Acceptance, or Production) * Double lane Cloud template upgrades are non-service affecting. * Keep your Deploy architecture current - less risk of the impact of Cloud template upgrade issues. == 5.

Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design & Deploy architecture aspects == 2. Key concepts == The eMagiz Cloud is the set of services and machines that make up together the engine in which the integrations are made active.

XL size **> 16Gb memory per machine === 3.3 Cloud sizing advice === In the [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]] you can see how your current machine(s) can be reviewed for available memory. === 3.4 Impact of Cloud sizing === The actual assigned machine size will be implemented in the Deploy architecture. In case your total runtime and machines are consuming more than the available memory of that specific size, the runtimes will not properly load and become disfunctional.

See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] for more information This count is also handy when verifying the actual assigned values in Deploy Architecture. == 4. Key takeaways == Part of the eMagiz platform is the Cloud which has specific upper limits for sizing.

Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design and Deploy Architecture phase. == 2. Key concepts == In the various microlearnings until the intermediate level, we have explained the [[eMagiz runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] itself .

Prerequisites == * Intermediate knowledge of the eMagiz platform * Good working experience in the Design phase Architecture and Deploy Architecture * Created several API gateway integrations == 2.