Shulou(Shulou.com)05/31 Report--

Configuration management ACM in the high availability service AHAS flow control degradation component application scenario is what, many novices are not very clear about this, in order to help you solve this problem, the following small series will explain in detail for everyone, there are people who need this can learn, I hope you can gain something.

Application Configuration Management (ACM) is an application configuration center product. Based on ACM, you can greatly reduce the workload of configuration management in microservices, DevOps, big data and other scenarios, while ensuring security compliance of configuration. ACM has a wealth of use scenarios, the following will introduce its application in AHAS flow control degradation.

What is AHAS Flow Control Degradation

AHAS flow control degradation is a professional flow control component oriented to distributed service architecture. It mainly takes traffic as the entry point to help you ensure the stability of services from multiple dimensions such as flow control, fuse degradation and system protection. At the same time, it provides powerful aggregation monitoring and historical monitoring query functions. In AHAS flow control degradation, we need to configure different rules (flow control rules, degradation rules, system protection rules, etc.) for different resources (such as service interfaces and methods). Because of the uncertainty of traffic, our rules also need to be dynamically managed according to the real-time situation of traffic. AHAS flow control degradation uses ACM as dynamic configuration center, and achieves the effect of real-time rule push by virtue of its real-time dynamic push ability.

How to use ACM

AHAS flow control degradation is divided into two parts: the client (based on open source Sentinel) and the AHAS console. Users only need to import AHAS Sentinel client dependency ahas-sentinel-client and specify relevant parameters at startup to access AHAS flow control degradation console, and view monitoring and configuration rules on AHAS console.

Sentinel abstracts out the dynamic data source interface, which can be easily connected to any configuration center. Sentinel recommends using dynamic rule sources in push mode. The push process is Sentinel Console → Configuration Center → Sentinel Data Source → Sentinel. It is very clear:

AHAS flow control degradation client provides ACM dynamic rule source adaptation and implements the logic of listening for remote rule changes, while AHAS flow control degradation console implements the corresponding rule push logic. When the user saves the rule in AHAS flow control degradation console, AHAS console will push the rule to the corresponding coordinate of ACM after saving the rule, and ACM will push the rule to the access terminal in real time. The dynamic configuration source of AHAS flow control degradation client will automatically register the listener corresponding to the current application coordinate to listen for rule changes, and when the change is detected, it will be loaded into the rule manager of Sentinel, and the new rule will take effect.

Did reading the above help you? If you still want to have further understanding of related knowledge or read more related articles, please pay attention to the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.