This document defines and explains the proper names and terms related to EDAS.
Ali-Tomcat is a container that EDAS relies on to run services. It integrates service publishing, subscription, service call tracing, and other core functions. You must publish applications in this container in both development and runtime environments.
Dubbo is a distributed service framework that provides high-performance and transparent RPC remote service calls. Dubbo is the core framework of Alibaba’s SOA service governance solution. Each day, over 2,000 services support over 3 billion access requests. This solution is widely used in various member sites of Alibaba Group.
EDAS, short for Enterprise Distributed Application Service, incorporates the tested and proven distributed products of the Alibaba middleware team as its core components. It provides highly available distributed solutions oriented to the enterprise-level cloud computing market and is a core product in Alibaba’s enterprise Internet architecture solution. EDAS makes full use of Alibaba Cloud’s resource management and service systems and introduces a whole set of mature distributed products from the middleware team. With EDAS, enterprise customers can easily build large-scale distributed application service systems.
EDAS Agent is a Daemon program installed on your ECS instances to implement communication between an EDAS cluster and the applications deployed on the ECS instances. It’s used for application management, status reporting, and information retrieval. It also serves as the communication channel between EDAS console and your applications.
EDAS RPC service
The EDAS RPC service provides support for the Dubbo framework. An application developed in the Dubbo framework and deployed with the WAR package can be published seamlessly with EDAS, and can be managed with service governance and data operation functions.
EDAS application life cycle
As the basic management unit in EDAS, an application usually contains multiple machines. EDAS provides a comprehensive application life cycle management solution, covering the entire process from application publishing to operation, including application creation, deployment, startup, rollback, scaling, disabling and removal, and so on.
EDAS EagleEye monitoring system
The EDAS EagleEye monitoring system analyzes distributed system calls, message sending, and database access to identify system bottlenecks and risks precisely.
EDAS application instance quota
This quota sets the maximum number of instances for all applications held by the primary account and its sub-accounts. When the billing account allocates a quota to each primary account, the sum of the quotas of all primary accounts bound to the billing account cannot be greater than the total application instance quota of the billing account.
As one of EDAS monitoring functions, it monitors many aspects of the application runtime status, including CPU, memory, load, network, and disk.
EDAS EagleEye analyzes every service call, sent message, and database access by the distributed system to help you precisely identify the bottlenecks and risks of the system.
Distributed configuration management
This EDAS function centrally manages distributed system configuration information in the EDAS Console. It can add, modify, and delete configurations in real time and can push configuration updates globally or within a specific application.
Distributed task scheduling
Distributed task scheduling allows you to configure any standalone or distributed tasks for periodic scheduling. You can also manage the periods and query the history of the tasks. This service is suitable for task scheduling scenarios, for example, migrating historical data at 02:00 every morning, triggering a task every five minutes, or sending a monthly report on the first day of each month.
High-Speed Service Framework (HSF) is designed to ensure the reliability and security of each distributed service call. Rigid service authentication is applied in every phase, from service registration to service subscription and service calling.
Contrary to rate limiting and throttling, service degradation pinpoints and blocks poor services that your application calls. This feature ensures the stable operation of your application and prevents the functionality of your application from being compromised by dependency on poor services. EDAS allows you to configure degradation rules based on response time, preventing your application from depending on poor services during traffic peaks.
Service call monitoring
This is another EDAS monitoring function. It can fully monitor the service calls made by your application in terms of the service QPS, response time, and error rate.
Rate limiting and throttling
EDAS allows you to configure throttling rules for the services provided by each application to ensure service stability. Throttling rules can be configured based on QPS and threads to ensure the system’s best operation stability during traffic peaks.
Automated load testing
The automated load testing tool helps you make performance testing a part of your daily routines. All the traffic for automated testing is the actual data in the production environment. By controlling the weights of each service, you can perform authentic online load testing without undermining stability.