To help you use Enterprise Distributed Application Service (EDAS), this topic describes how to deploy the microservices application demos of Spring Cloud and Apache Dubbo to different EDAS environments. A demo can be deployed to an EDAS environment within 30 minutes.
EDAS provides one to five pay-as-you-go application instances for free. If you have activated pay-as-you-go Standard Edition for EDAS and deployed no more than five application instances, you are not charged for using EDAS. However, you must pay for the Alibaba Cloud resources that you use to create Elastic Compute Service (ECS) and Server Load Balancer (SLB) instances until you release these resources.
Nacos is used as the registry for the application demo that is provided by EDAS. You can also create a registry or use Microservices Engine (MSE) to host another type of registry, such as Eureka or ZooKeeper, based on your business requirements. Make sure that the registry and the environment in which applications are to be deployed are connected over a network. If this condition is met, you can deploy your applications to EDAS without modifying code and use the application management, microservices, and cloud-native Platform as a Service (PaaS) platform capabilities of EDAS. For more information, see What is EDAS?
Default environment: the default ECS cluster in the default virtual private cloud (VPC) and default microservices namespace that are provided by EDAS. EDAS provides a default environment only for ECS clusters but not for Kubernetes clusters.
Custom environment: the ECS cluster or Kubernetes cluster that you create.