This Quick Start shows you how to deploy Spring Cloud and Apache Dubbo (Dubbo) demo microservice applications to different environments in EDAS. Each deployment scenario takes less than 30 minutes to complete.
EDAS provides one to five free pay-as-you-go application instances. If you activate the pay-as-you-go Standard Edition of EDAS and deploy no more than five application instances, you are not charged for using EDAS. However, you are charged for the Alibaba Cloud resources that you use, such as Elastic Computing Service (ECS) instances and Server Load Balancer (SLB) instances, until you release them.
The demo applications provided by EDAS use Nacos as the registry. You can also build your own registry, or use a registry hosted by MSE, such as Eureka or ZooKeeper. If the registry and the application deployment environment can communicate over the network, you can deploy applications to EDAS without changing any code. This lets you use the application hosting, microservice, and cloud-native Platform as a Service (PaaS) capabilities of EDAS. For more information, see What is Enterprise Distributed Application Service (EDAS)?.
-
Default environment: The environment that contains the default ECS cluster, default VPC, and default microservices namespace provided by EDAS. EDAS currently provides a default environment only for ECS clusters. No default environment is available for Kubernetes (K8s) clusters.
-
Custom environment: An ECS or K8s cluster that you create.