Adhesive framework-Introduction to Configuration Service Module

First, let's talk about the background of the Configuration Service. In a complex system, some parts may be subject to regular changes, which may be the system itself or the business needs. Considering the flexibility and scalability of the system, we use the frequently-modified part as the parameter configuration to achieveCodeTo adjust the system functions and business logic. Such as some large systems, such as SAP, is a good example. The system can adjust the Business Process of the software by setting 6000 "switches. We usually use a local configuration file (XML) to save configuration information. The disadvantage of using a configuration file is also obvious. As our system grows larger, there will be more and more configuration files, configuration file updates are troublesome even when a large number of servers are required, and the consistency of configuration file versions on each server is hard to guarantee. Our idea is to save the configuration in the database for centralized management, and then manage the configuration with the Web Background.

Configure the service target:

1. centrally manage configurations. Different configurations can be divided based on different applications;

2. After the configuration is modified, the client will be notified in time to ensure that the latest configuration is obtained each time;

3. More data types are supported. In addition to basic data types (such as integer, String, Boolean, enumeration, floating point, and date), list, dictionary, and custom entity are also supported;

4. Horizontal resizing is supported.

Configuration service module division:

There are two parts:

1. Server

The server uses WCF to encapsulate basic operations (ADD, modify, and query) for incremental configuration and configuration as a service for the client to call. When the pressure on one configuration service is too high, you can add another one and use F5 for load balancing.

2. Client

In order to obtain configuration requests that are not frequently sent to the configuration server, the configuration will be cached locally. To maximize performance, the configuration can be classified into level-1 cache and level-2 cache. One level cache caches configuration items, and the second level cache caches the configuration values (for dictionaries, lists, and custom configuration entities, multiple configuration items are included ), the local cache is automatically updated by the synchronization module.

Configure service module features:

This article introduces the configuration service module.ArticleWe will introduce you to the use of the configuration service module.