Helps you install a properly configured application best practice in a cloud device

A common scenario for deploying applications into the cloud is a scenario with non-cloud software you want to integrate these non-cloud software into software that is already running in the cloud, there are several features that need to be planned (if you are still fixing the problematic application) or integrated (if the application already exists). In this article, the authors provide 18 best practices to ensure that your application can easily be integrated into another cloud product, easily integrated into another cloud device, or hosted in the cloud as a stand-alone device.

This article provides several best practices for designing and packaging applications into a cloud environment so that the application can:

Integrated into another cloud product so that other products can take advantage of its capabilities.
Integrated into an application that has been hosted in the cloud.
Hosted in the cloud as a stand-alone device.
If you are interested in these scenarios, read this article to learn about the experiences we have incorporated into best practices to achieve any of these goals.

Let's start with a detailed discussion of these scenarios.

3 scenes

Let's say again that these scenarios include integrating an application into an existing cloud product, deploying an application as part of an entire device package, or integrating an application into an existing cloud device.

Integrate your application into another cloud product

The current requirement is to enhance existing cloud applications and your application capabilities. The goal is to achieve seamless integration.

Typically, when you need to introduce new functionality into existing products, you are involved in designing and developing new features from scratch, and another option is to integrate their functionality into the cloud by leveraging an existing product (in which case, you do not need to enable the cloud). In this case, you must make sure that your application can connect to the existing cloud product correctly.

Add your application to another device hosted in the cloud

A cloud device is made up of preinstalled and preconfigured software and applications, and can sometimes be used as a self-contained server. When you plan to add an additional application to an existing cloud device package to enhance its functionality, make sure that your application can interact correctly with other applications and configuration files in the package as well as with device resource dependencies.

Hosting your application as a stand-alone cloud device

One way to use your application in a cloud environment is in its own cloud device, especially if you do not need to integrate it with another cloud application.

Before continuing, it is helpful to know what we call devices, applications, and virtual machines:

Virtual Appliance: A pre-built software solution consisting of one or more virtual machines packaged, maintained, updated, and managed as a unit. Http://www.aliyun.com/zixun/aggregation/7155.html "> Developers create virtual devices by developing self-contained and optimized application stacks that are customized for their workloads and embedded in an optional operating system These devices are more secure and reliable than traditional software; You can use the application only if you copy a set of files and turn on the virtual device.
Application: A cloud-enabled application that performs a function or a set of functions. It is a component of the application stack in the device.
Virtual machines: Create a tightly isolated software container to run on a virtualized platform. It contains 4 virtualized resources: CPU, RAM, memory, and network.
In this article, the word "product" is used to refer to "application" or "device", depending on the context.

Now, let's look at the best practices that can help these scenarios become reality.

Practice 1: Support silent installation

The installation process does not display messages or Windows installed as a silent installation. Silent installation is not an unattended installation. Unattended installation is an installation that requires no user interaction; a silent (or silent) installation is an installation that does not display any process instructions.

You must support silent installation and interactive/gui installation in your product so that customers can choose either method to install the product. For a silent installation, the input that the user needs should be given in a response file that only needs to be edited at the beginning of the installation. After the installation begins, no user data is required or the installation process/window is displayed to the user.

When you integrate an application into another application or a device, it becomes part of a single product, and a single installer is the preferred creation. If your product cannot be installed silently, information from the user is requested for your product during a single installation, and the device team may not want to show/ask its users. This is a hassle for users, and they don't need to know the details of these basic products. If a silent installation is not available, you will lose the efficiencies that have been achieved because, for users, it is like installing two different products.