Skip to Content

Impact of Cloud template upgrades

Last modified by Erik Bakker on 2024/09/03 07:58

In this microlearning, we’ll explore the concept of cloud templates within eMagiz. A cloud template defines how your architecture will be deployed on AWS, including which tools and configurations are available. We’ll discuss the impact of upgrading these templates, including considerations for service interruptions, update durations, and best practices for managing changes. Understanding these factors will help you effectively plan and execute cloud template upgrades while minimizing disruptions to your environment.

Should you have any questions, please get in touch with academy@emagiz.com.

1. Prerequisites

  • Advanced knowledge of the eMagiz platform
  • Completed the relevant microlearnings around Cloud Management till advanced.

2. 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.

Cloud Templates:

  • Determine what runtime runs where
  • Determine which eMagiz Cloud version we will use
  • Determine which supporting tools are available
  • Are updateable

3. Assessing the impact of upgrading Cloud templates

The following considerations are valid when upgrading to a new Cloud template.

  • Service affecting vs. non-service effecting
    • Non-service affecting templates will not affect your current operation. * flows will continue to function as usual. You can safely apply the cloud template. Service affecting means that the machines will need to be stopped and started to operationalize the cloud template. There is a short window in which flows are not operational, and there will be a delay in message delivery & processing. Messages are preserved.
  • Other changes pending for an AWS update
    • The apply to environment button will apply all the changes made in Design architecture and Deploy architecture. These can be things such as
      • Memory changes
      • Runtimes removed
      • Runtimes added
Information

It is a good practice to isolate the Cloud template upgrade from these changes to the AWS slot. 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.

  • 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. Take this value into account when making the plan to upgrade or set the automatic upgrade timeslot.
  • Availability zone
    • The Cloud template upgrade will perform the upgrade zone by zone for failover setups. Two zones (A and B) are defined in the failover scenario. Effectively, this means there is no downtime in the entire environment as flows, and the JMS server will continue operating as usual.
  • Multiple Cloud template upgrades
    • If you have a backlog of upgrades, please take each cloud template step by step. If you switch to an automatic upgrade, this upgrade will take making all the upgrades.

4. Key takeaways

  • Cloud templates can be rolled out automatically via the upgrade options. 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. Suggested Additional Readings