Review Finishing - EDAS

EDAS :
EDAS supports languages ​​Java, C++, PHP. EDAS supports Idea, Eclipse; Eclipse plug-in installation and other compilation tools. The primary version of EDAS only supports application deployment management and does not support the HSF function. EDAS Basic does not support the RPC framework.
EDAS provides a high-performance RPC framework, which can build a highly available distributed system, considering the details of distributed service discovery, service routing, service invocation, and service security between applications. EDAS can be independently deployed to the company intranet.
The EDAS HSF service framework ensures the stability and security of each distributed call by the user. Strict service authentication is performed in the links of service registration, service subscription, and service invocation.
HSF setting timeout: Configured through HSF tags methodSpecials and clientTimeout, the priority is from high to low: client methodSpecials>clientclientTimeout>server methodSpecials>server clientTimeout
EDAS console domain name: https://edas.console. The aliyun.com
EDAS console provides the log browsing function to view the running logs of the applications deployed on the server. Convergence logs are used to merge and sort similarly formatted logs in a single application. It takes about 5 minutes for the convergence log configuration to take effect.
EDAS installs the lightweight configuration center: starting the configuration center will occupy ports 8080 and 9600 of this machine, you need to add {light configuration center public network ip} jmenv.tbsite.net to the hosts. If this machine has multiple network cards, you can add startup parameters to the startup script startup.bat or startup.sh: -Daddress.server.ip={specified IP address}; specify the service to be registered by the -Dhsf.server.ip parameter IP.
The throttling rules for EDAS service throttling (the throttling rules are only applicable to service providers) can be configured from the two dimensions of QPS and threads. HSF current limiting and HTTP current limiting can be performed.
EDAS provides the configuration of degradation rules (degradation rules are only suitable for service consumers) from the dimension of response time.
EDAS Eagle Eye Monitoring System can analyze every system call, message sending and database access of distributed system. It mainly includes application topology (you can view call topology and traffic QPS), call chain query (you can view slow services and error services), and call chain details (based on TraceId query).
EDAS provides an alarm function, but currently there are only SMS and email notifications.
EDAS applications are mainly divided into two types: middleware service applications (JAR/WAR package type common applications and Docker applications) and Kubernetes applications. Kubernetes applications only support VPC networks.
There are two types of application deployment in EDAS: ECS exclusive instance (on an independent ECS machine, only one application is allowed to be deployed), Docker instance (only one instance can be deployed on the same ECS for a single application)
EDAS can target the application Service invocation, and comprehensively monitor the QPS, response time (RT) and error rate of the service.
EDAS can monitor the basic indicators of the machine such as CPU, memory, load, network and disk in detail according to the running status of the application. EDAS also provides container monitoring capabilities (application diagnostics). Basic monitoring (which can provide application-dimensional data) is for machines, and container monitoring is for containers where applications are located. There is a delay in basic monitoring, and container monitoring is basically real-time.
EDAS provides the elastic scaling function to automatically expand or shrink according to the three indicators of CPU, RT, and Load of the servers in the cluster.
EDAS manages the application lifecycle, including creation, deployment, start/stop, and deletion (application deletion cannot be recovered). You can set JVM parameters, Tomcat parameters, group application instances (you can deploy applications in groups, add instances to groups), and configure load balancing. Configurable health check URL.
EDAS includes two types of clusters: Swarm (deploy common applications and Docker applications) and Kubernetes cluster (deploy Kubernetes applications).
The configuration push of EDAS is divided into global configuration push and configuration push within the application. The global configuration push can operate all the configuration information of the user, and the configuration push in the application can only operate the configuration information to which the application belongs. A configuration information consists of triples (group, DataId, Content).
EDAS provides a system of master and sub-accounts. All paid accounts are master accounts (with all EDAS resources and all permissions), but not all master accounts are paid accounts. A paid account can be bound to a maximum of 5 main accounts. The RAM sub-account is created by the main account in the RAM system, and the sub-account name must be unique within the main account. There are two authorization methods for RAM accounts: RAM authorization and EDAS authorization (the two methods are mutually exclusive. With RAM authorization, authorization in EDAS is not possible). The main account can assign permissions to the bound sub-accounts (users). resource allocation, etc. The authorization of the application can only be authorized by the main account to the sub-account.
The resources of EDAS mainly refer to the three types of cloud server ECS (Elastic Compute Service), load balancing SLB (Server Load Balancer), and VPC (Virtual Private Cloud).
The VPC environment call chain and monitoring data are generated only when there is access request traffic. If no customers visit the website, there will be no curve. Make sure the machine's port 8182 is open. Run netstat -antp|grep 8182 to check whether the port is open.
EDAS Agent is a Daemon program installed on the user's ECS in EDAS. It is mainly used for communication between the EDAS service cluster and the applications deployed on the corresponding ECS. During the running process, it is mainly responsible for application management, status reporting, and information acquisition. and other functions, the installation script of Edas Agent in each area is different. If Java is found to be uninstalled during the Agent installation, it means that the specified JDK version is inconsistent with the installed version; if the heartbeat of the EDAS Agent stops, the real-time status of the ECS will become the Agent exception. At this time, any deployment, start, or stop of the ECS and other commands are invalid. After restarting the server, EDAS Agent will automatically restart, but Tomcat will not. If you configure JVM parameters (only valid for EDAS Agent 2.8.0 and above), the parameters will be written to the bin/setenv.sh file in the container directory, and you need to restart Tomcat and the application to take effect.
The EDAS container consists of AliTomcat, Pandora and custom Pandora plugins. EDAS container releases do not have any impact on deployed applications.
Ali-Tomcat is a container that services in EDAS must rely on when running. It mainly integrates a series of core functions such as publishing, subscription, and call chain tracking of services. Whether it is a development environment or runtime, applications must be published in this container. middle.
Pandora is a lightweight isolation container, namely taobao-hsf.sar, which is used to isolate the dependencies between Web App and middleware, and isolate the dependencies between middleware so that they do not affect each other.
The customized Pandora plug-ins integrate various middleware product plug-ins such as plug-ins for service discovery, plug-ins for configuration push, and plug-ins for call chain tracking. Perform all-round operation and maintenance management of EDAS applications such as service monitoring, governance, tracking, and analysis.
The traffic management rules of EDAS Advanced Edition have two modes: parameter modulo and list diversion. Typically used for grayscale releases, blue-green deployments, A/B testing, marketing needs (new product launches).
EDAS provides Open API, which can provide resource query, application life cycle management and account management functions.
EDAS Log Collector (Queqiao): Only supports CentOS 6.5/7.0/7.2 64-bit and Ali-Linux 15.1 64-bit, can be installed on multiple machines, it is recommended to install it on the machine where EDAS Agent is installed (not required) . After the installation is complete, manually check whether the port (8000) is established successfully.
Dubbo is a first-generation RPC framework.