To help you experience EDAS, Quick Start describes how to deploy microservice application demos based on Spring Cloud and Apache Dubbo (Dubbo for short) to different EDAS environments. Each deployment scenario can be completed 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 deploy 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 the 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 MSE to host another type of registry, such as Eureka or ZooKeeper, based on your requirements. Make sure that the registry and the environment where the applications are to be deployed are connected over a network. If this condition is met, you can deploy your applications to EDAS and use the application hosting, microservices, and cloud native application PaaS platform capabilities of EDAS without modifying code. For more information, see What is EDAS?.
- Default environment: the default ECS cluster in the default VPC and the default namespace that are provided by EDAS. EDAS provides a default environment for only ECS clusters but not for Kubernetes clusters.
- Custom environment: the ECS cluster or the Kubernetes cluster that you create.