Custom combination mode - Enterprise Distributed Application Service

Enterprise Distributed Application Service (EDAS) is a platform as a service (PaaS) platform for cloud-native applications. When you activate EDAS, you can choose the integrated mode or the custom combination mode. In integrated mode, EDAS integrates application lifecycle management, Application Real-Time Monitoring Service (ARMS), and Microservice Engine (MSE). In custom combination mode, you can combine these three functions based on your needs. Application lifecycle management, a basic capability of EDAS, is free of charge. You can activate ARMS or MSE based on your needs or use your own application monitoring system, such as SkyWalking.

Background information

After you activate EDAS in integrated mode, you do not need to purchase MSE and ARMS independently. ARMS provides the application monitoring function and MSE provides the microservices governance function. We recommend that you use the integrated mode for production applications.

However, you may not need complete MSE and ARMS capabilities in some scenarios (such as when you develop and test applications), or you already have a microservices governance or application monitoring system (such as open-source SkyWalking). The integrated mode is not suitable in these cases. Therefore, to better meet the needs of different scenarios, EDAS offers a custom combination mode. You can activate MSE and ARMS services as needed or use your own monitoring system to reduce costs.

Comparison between the two modes

Integrated mode
In this mode, EDAS integrates application lifecycle management, MSE, and ARMS. After you activate EDAS by using the subscription or pay-as-you-go billing method, you can use MSE and ARMS by default. You do not need to pay additional fees for them. If you need to use MSE and ARMS to manage your application, the integrated mode of EDAS lowers your costs.

Custom combination mode

In this mode, EDAS only provides application lifecycle management for free, while you can activate MSE and ARMS as needed. EDAS does not bill applications that are created in custom combination mode by using the subscription or pay-as-you-go method. In this case, you use EDAS free of charge.

When MSE and ARMS are not activated, EDAS only supports the following functions:

Item	Function	Standard Edition	Professional Edition	Platinum Edition
Microservices framework	Microservices framework	Supports Spring Cloud, Dubbo, and High-speed Service Framework (HSF).
Application release and O&M	Application lifecycle management	Allows you to create, deploy, roll back, start, stop, restart, delete, and scale up applications.
	Log	Allows you to query online logs and log files, and integrates with Log Service.
	Auto scaling	Supports manual scaling and auto scaling (scheduled scaling or metric-based auto scaling). Note If ARMS is not activated, scaling based on response time and queries per second (QPS) is not supported. For more information about activating ARMS, see Activate ARMS.
	Continuous integration and continuous delivery (CI/CD)	Supports OpenAPI SDK and integration with Jenkins plug-ins and the latest version of Apsara DevOps.
	Release	Supports at-a-time release or phased release, but not canary release.
	Registration and configuration center	Supports distributed registration and configuration centers.
Enterprise permission management	Access control	Supports isolation among tenants and permission policies of Resource Access Management (RAM).
	Multi-environment management	Allows you to use namespaces to isolate resources and create multiple environments, including the development, test, and production environments.
	Hybrid cloud	Not supported.	Allows you to deploy applications across Elastic Compute Service (ECS) clusters in hybrid cloud architecture. Allows you to deploy applications across Kubernetes clusters in hybrid cloud architecture.
Monitoring	Monitoring	Only supports the Prometheus monitoring feature.

Note

EDAS does not provide a registration SLA guarantee for applications in custom combination mode if MSE is not activated.

Scenarios

The custom combination mode is suitable in the following scenarios:

Applications in development and test environments do not require MSE and ARMS.
Users have their own monitoring systems and do not need ARMS.
A monolithic application does not require MSE.

Limits

Currently, the custom combination mode is in public preview and is available only in the China (Chengdu) region.
The custom combination mode is suitable only for Kubernetes clusters.
The custom combination mode is suitable only for Java applications.

Procedure

Log on to the EDAS console. In the left-side navigation pane, choose Application Management > Applications. In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace. In the upper-left corner of the Applications page, click Create Application.

In the Basic Information step, set the parameters in the Cluster Type and Application Runtime Environment sections and click Next.

Parameter	Description
Cluster Type	The type of the cluster in which you want to deploy the application. Select Kubernetes Clusters.
Application Runtime Environment
Hosted Applications	Select Java.
Select Application	Select Java, Tomcat, or EDAS-Container (HSF) based on your application type and deployment package. For information about how to deploy an application by using an image, see Use an image to deploy a Java microservices application in a Kubernetes cluster. Java: Select this option if you want to use a universal JAR package to deploy the application as a Dubbo or a Spring Boot application. You can set the Java Environment parameter after you select this option. Tomcat: Select this option if you want to use a universal WAR package to deploy the application as a Dubbo or Spring application. You can set the Java Environment and Container Version parameters after you select this option. EDAS-Container (HSF): Select this option if you want to use a WAR or fat JAR package to deploy the application as an HSF application. You can set the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after you select this option.
Monitoring and Governance Solution	Integrated Solution: This mode is suitable for scenarios where both ARMS and MSE are required for applications in production environments. This mode is cost-effective. Custom Combination Solution: This mode is suitable for scenarios where users deploy monolithic applications or have their own application monitoring or microservices governance systems.

In the Configurations step, configure the environment information, basic information, and deployment method for the application, set the related resource parameters, and then click Next. For more information, see Use a JAR or WAR package to deploy an application in an ACK cluster and Use an image to deploy a Java microservices application in a Kubernetes cluster.
(Optional) In the Advanced Settings step, set other configurations of the application. For more information, see Configure scheduling rules.
After you configure the advanced settings, click Create Application. In the Creation Completed step, click Create Application.
In the Confirm Application Change Precheck dialog box, click Start Precheck.
1. After the data in the dialog box is refreshed, confirm the precheck items and results and click Continue.
2. Optional:If you modify the preceding precheck items, click Check Again.
The application requires several minutes to be deployed. During the process, you can view the change records to track the deployment progress of the application on the Change List page. After you deploy the application, go to the Application Overview page to view the running status of pods. If the pods are in the running state, the application is deployed. You can click the running status of pods to view the Deployments, pods, and advanced configurations of the application instances.

What to do next

After you deploy the application, add an Internet-facing Server Load Balancer (SLB) instance to allow access to the application over the Internet. You can also add an internal-facing SLB instance so that all the nodes in the same VPC can access the application by using this internal-facing SLB instance. For more information, see Bind CLB instances or Reuse a CLB instance.