A configuration center management method and management system of a freight rate query system

Abstract

The application discloses a configuration center management method and system of a fare query system, and belongs to the field of distributed system management. The configuration center management method adopts a modular architecture to realize dynamic synchronization of configuration data, and comprises the following steps: a configuration center service management module initializes a client instance through a data source configuration file, and uses an adapter to obtain a data source configuration and a version number; based on the version number, configuration data is loaded to a data management module, and a task scheduling module creates a listening task; a command interaction interpreter parses a user instruction to call the configuration data, the task scheduling module listens to configuration changes in real time and synchronously updates, and thus the configuration center management of the fare query system is realized. Through the version control and real-time listening mechanism, the application significantly improves the accuracy and timeliness of the fare configuration management.

Description

Technical Field

[0001] This invention belongs to the field of distributed system configuration management technology, specifically relating to a configuration center management method and management system for a fare query system. Background Technology

[0002] Against the backdrop of the booming global civil aviation industry and the continuous expansion of economic globalization, the air transport industry has ushered in unprecedented development opportunities. This trend has not only led to the emergence of one or more airlines in most countries around the world, but has also spurred the development of a vast number of airport facilities, as well as intricate route networks and corresponding fare data systems. With the surge in the number of routes and the increasing complexity of fare data, the cluster size of fare query systems is constantly expanding, posing significant challenges to the configuration management and status synchronization of various service nodes within the system. How to efficiently manage these clusters and ensure the status synchronization of various service nodes within the cluster has become a critical technical problem that urgently needs to be solved.

[0003] In traditional management models, each service node often operates independently, lacking a unified management and scheduling mechanism, leading to frequent inconsistencies in configuration data and update delays. This not only affects the accuracy and timeliness of fare inquiries but also increases the complexity and cost of system maintenance. Especially when facing large-scale configuration data updates, ensuring that each service node can obtain and apply the new configuration data in a timely and accurate manner has become a pressing technical challenge. Furthermore, as the system architecture continues to evolve, effectively preserving and rolling back historical configuration data to ensure the correct collaborative operation of all service nodes in the cluster has also become another significant technical challenge. Summary of the Invention

[0004] To overcome the limitations of existing technologies, this invention provides a configuration center management method and management system for a fare query system. This system enables unified management of cluster configuration and node configurations, supports version management of configuration data, and facilitates rollback and backup operations. During configuration updates, this invention can promptly and accurately distribute the updated configurations to the services, ensuring that all service nodes can operate correctly and collaboratively.

[0005] This invention is achieved through the following technical solution: In one aspect, the present invention provides a configuration center management method for a fare inquiry system, the configuration center management method comprising: Step S1: The configuration center service management module initializes each service instance of the client in the configuration storage system according to the data source configuration file, and configures the client operations that connect to various data sources through the adapter to obtain the configuration data and version number of the data source. Step S2: Based on the version number information of the configuration data, the configuration center service management module loads the configuration data in the storage system into the configuration center data management module. At the same time, the configuration center task scheduling module creates a configuration data listening task in the configuration storage system. Step S3: The configuration center command interaction interpreter parses the user-input commands, enabling the fare query system to call the configuration data. During the call, the configuration center task scheduling module monitors changes in the configuration data in the configuration storage system and synchronizes the new configuration data to the configuration center data management module, thereby realizing the configuration center management of the fare query system.

[0006] Furthermore, in step S1, the storage system refers to a storage system capable of storing data, including relational database systems or non-relational database systems, such as the ZooKeeper distributed file storage system and the Redis memory-based distributed storage system; the service instances of the client are service instance objects that connect to data sources and provide different service operations.

[0007] Furthermore, in this embodiment, please refer to Figure 2 In step S2, based on the version number information of the configuration data, the configuration center service management module loads the configuration data from the storage system into the configuration center data management module. Simultaneously, the configuration center task scheduling module creates a configuration data listening task in the configuration storage system, specifically including: Step S201: The configuration center service management module reads the version number of the configuration data passed by the virtual machine parameters, and locates the configuration data storage path according to the configuration path parameters and the version number to obtain the corresponding configuration data; Step S202: Based on the configuration data, the configuration center service management module generates a snapshot on the configuration node (configuration data storage path) of the corresponding version of the configuration data in the storage system, configures the cache node of the corresponding version of the configuration data according to the snapshot, loads the full configuration data to the cache node, and at the same time, the configuration center task scheduling module creates a listening task to listen to the configuration data under the corresponding cache node. Step S203: Based on the service identifier and merging rules, merge and cache the data under the cache node and load it into the configuration center data management module.

[0008] Furthermore, in step S202, configuring cache nodes for the corresponding version of configuration data based on the snapshot specifically involves configuring three data cache nodes for the same version of configuration data based on the generated snapshot: a default configuration data cache node, a cluster configuration data cache node, and a single-point configuration data cache node, wherein: The single-point configuration data cache node is for configuring parameter data for a single service instance; the cluster configuration data cache node is for configuring parameter data for multiple service instances in a cluster; the default configuration data cache node is used when the configuration parameters are not present in either the cluster or single-point configuration data.

[0009] Furthermore, in step S203, the service identifier includes IP and machine name; the merging rule refers to, for configuration data of the same module and the same attribute, executing the cluster configuration data to overwrite the default configuration data and the single-point configuration data to overwrite the cluster configuration data.

[0010] Furthermore, in this embodiment, please refer to Figure 3 In step S3, the configuration center command interaction interpreter parses the user-input commands to enable the fare query system to call configuration data. Specifically, the configuration center command interaction interpreter enters command interaction mode through startup parameters, including: Enter the command interaction mode by starting the parameters, and then enter the command parameters in the command interaction window; The configuration center command interaction interpreter parses the command parameters, and after parsing, determines whether to exit execution. If execution does not exit, the configuration operation of the corresponding command will be executed and the execution result notification will be returned. If execution exits, the interactive mode will be exited.

[0011] Furthermore, the commands include insert, update, query, and delete commands.

[0012] Furthermore, in step S3, the changes in the configuration data include hot updates, migrations, version number upgrades, and version number rollbacks. Furthermore, the configuration center task scheduling module monitors changes in configuration data in the configuration storage system and synchronizes the changed new configuration data to the configuration center data management module, thereby realizing configuration center management of the fare query system, including: Step S301: When the configuration data changes, the configuration data version number is upgraded, and the configuration data version number upgrade management of the fare query system is implemented. Step S302: When the configuration data changes, the configuration data migration management of the fare query system is implemented during configuration data migration. Step S303: When the configuration data changes, such as during hot updates and version rollbacks, the configuration data of the fare query system is managed for hot updates and version rollbacks.

[0013] Furthermore, in this embodiment, please refer to Figure 4In step S301, the change in configuration data refers to the upgrade and management of the configuration data version number of the fare query system when the configuration data version number changes. The specific implementation steps include: Step S301-1: Read the old version number of the configuration data, load the old version configuration data and generate a snapshot, and import the old version configuration data into the local backup file based on the generated snapshot; Step S301-2: Read the new version number and create a new version configuration node, and import the configuration data from the local backup file into the new version configuration node; Step S301-3: Modify the new version configuration data through the configuration center interactive commands to complete the version number upgrade management of the configuration data.

[0014] Furthermore, in this embodiment, please refer to Figure 5 In step S302, the change in configuration data refers to the configuration data migration management of the fare query system during configuration data migration. The specific implementation process includes: Step S302-1: The configuration center client loads and finds the version number of the configuration data to be migrated and the corresponding configuration data according to the configuration data migration command, and exports the configuration data to be migrated to the configuration data backup file; Step S302-2: Load the new data source configuration and create a corresponding version number configuration cache node in the new data source; Step S302-3: Import the configuration data from the configuration data backup file into the cache node configured with the version number corresponding to the new data source to complete the configuration migration.

[0015] Furthermore, in step S303, the changes in configuration data occur when configuration data is hot-updated, i.e., when a certain piece of configuration data is modified, causing this piece of configuration data to change. At this time, the configuration center monitoring task will detect this change, read the change information and hand it over to the configuration center data management module. The configuration center data management module will update this configuration data and reorganize the cached configuration data according to the rules. The changes in configuration data also occur when the configuration data version number is rolled back. A certain old version number is specified through virtual machine parameters and passed to the configuration center service management module. The configuration center service management module loads the old version configuration data according to the old version number, completing the configuration data version rollback to the historical version operation.

[0016] In another aspect, the present invention provides a configuration center management system for a fare inquiry system, used to execute a configuration center management method for a fare inquiry system as described above, the configuration center management system comprising: The configuration center service management module is used to initialize the service instances of the clients in the configuration storage system according to the data source configuration file, and to configure the client operations that connect to various data sources through the adapter, and to obtain the configuration data and version number of the data source. The configuration center data management module is used to receive and store configuration data from the configuration center service management module; The configuration center task scheduling module is used to create configuration data listening tasks in the configuration storage system, listen for changes in configuration data, and synchronize the new configuration data to the configuration center data management module. The configuration center command interaction interpreter is used to parse user-input commands and enable the fare query system to call configuration data.

[0017] Compared with the prior art, the present invention has significant advantages: First, this invention supports heterogeneous data sources such as ZooKeeper and Redis through a unified adapter, completely solving the problems of traditional solutions relying on a single storage system and high migration costs. Second, this invention innovatively adopts a three-level caching strategy (default configuration → cluster configuration → single-point configuration) and formulates priority coverage rules (single-point covers cluster, cluster covers default), combined with service identifiers (IP / machine name) to achieve fine-grained hierarchical management of configurations, meeting the differentiated needs of complex business scenarios. Third, relying on the task scheduling module to monitor configuration changes in real time (hot update / migration / version upgrade / rollback), and through the snapshot mechanism and command-line interaction mode (insert / update / query / delete commands), it achieves dynamic second-level synchronization and visualized operation and maintenance of configuration data, significantly improving system availability. Fourth, the automated version management process (old version snapshot backup → new node creation → data migration → version rollback) greatly reduces the risk of manual operation, ensuring that the fare query system completes the full lifecycle management of configurations without interruption.

[0018] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating the configuration center management method of a fare inquiry system.

[0021] Figure 2 This is a schematic diagram of the command interaction function of the configuration center.

[0022] Figure 3 This is a schematic diagram of the configuration data loading process.

[0023] Figure 4 This is a schematic diagram of the configuration data version management process.

[0024] Figure 5 This is a schematic diagram of the configuration data migration process. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0026] Example 1: In this embodiment, as Figures 1-5 This provides a configuration center management method for a fare inquiry system. Please refer to [link / reference]. Figure 1 The configuration center management method includes: Step S1: The configuration center service management module initializes each service instance of the client in the configuration storage system according to the data source configuration file, and configures the client operations that connect to various data sources through the adapter to obtain the configuration data and version number of the data source. Step S2: Based on the version number information of the configuration data, the configuration center service management module loads the configuration data in the storage system into the configuration center data management module. At the same time, the configuration center task scheduling module creates a configuration data listening task in the configuration storage system. Step S3: The configuration center command interaction interpreter parses the user-input commands to enable the fare query system to call the configuration data. During the call, the configuration center task scheduling module monitors the changes in the configuration data in the configuration storage system and synchronizes the new configuration data to the configuration center data management module, thereby realizing the configuration center management of the fare query system. in: The configuration center service management module is used to manage various service instances, including export configuration data service, import configuration data service, and command interaction service; The adapter is used to adapt to client operations that connect to various data sources, and to solve the problem of data operation differences between different data sources; The configuration center data management module is used to store and manage configuration data; The configuration center command interaction interpreter is used to parse user-input commands in command interaction mode; The configuration center task scheduling module is used to create and destroy various task threads in the configuration center.

[0027] Furthermore, in step S1, the storage system refers to a storage system capable of storing data, including relational database systems or non-relational database systems, such as the ZooKeeper distributed file storage system and the Redis memory-based distributed storage system; the service instances of the client are service instance objects that connect to data sources and provide different service operations.

[0028] Furthermore, in this embodiment, please refer to Figure 2 In step S2, based on the version number information of the configuration data, the configuration center service management module loads the configuration data from the storage system into the configuration center data management module. Specifically, loading the configuration data includes: Step S201: The configuration center service management module reads the version number of the configuration data passed by the virtual machine parameters, and locates the configuration data storage path according to the configuration path parameters and the version number to obtain the corresponding configuration data; Step S202: Based on the configuration data, the configuration center service management module generates a snapshot on the configuration node (configuration data storage path) of the corresponding version of the configuration data in the storage system, configures the cache node of the corresponding version of the configuration data according to the snapshot, loads the full configuration data to the cache node, and at the same time, the configuration center task scheduling module creates a listening task to listen to the configuration data under the corresponding cache node. Furthermore, in step S202, configuring cache nodes for the corresponding version of configuration data based on the snapshot specifically involves configuring three data cache nodes for the same version of configuration data based on the generated snapshot: a default configuration data cache node, a cluster configuration data cache node, and a single-point configuration data cache node, wherein: The single-point configuration data cache node is for configuring parameter data for a single service instance; the cluster configuration data cache node is for configuring parameter data for multiple service instances in a cluster; the default configuration data cache node is used when the configuration parameters are not present in either the cluster or single-point configuration data.

[0029] Step S203: Based on the service identifier and merging rules, merge and cache the data under the cache node and load it into the configuration center data management module.

[0030] Furthermore, in step S203, the service identifier includes IP and machine name; the merging rule refers to, for configuration data of the same module and the same attribute, executing the cluster configuration data to overwrite the default configuration data and the single-point configuration data to overwrite the cluster configuration data.

[0031] Furthermore, in this embodiment, please refer to Figure 3 In step S3, the configuration center command interaction interpreter parses the user-input commands to enable the fare query system to call configuration data. Specifically, the configuration center command interaction interpreter enters command interaction mode through startup parameters, including: Enter the command interaction mode by starting the parameters, and then enter the command parameters in the command interaction window; The configuration center command interaction interpreter parses the command parameters, and after parsing, determines whether to exit execution. If execution does not exit, the configuration operation of the corresponding command will be executed and the execution result notification will be returned. If execution exits, the interactive mode will be exited.

[0032] Furthermore, the commands include insert, update, query, and delete commands.

[0033] Furthermore, in step S3, the changes in the configuration data include hot updates, migrations, version number upgrades, and version number rollbacks. Furthermore, the configuration center task scheduling module monitors changes in configuration data in the configuration storage system and synchronizes the changed new configuration data to the configuration center data management module, thereby realizing configuration center management of the fare query system, including: Step S301: When the configuration data changes, the configuration data version number is upgraded, and the configuration data version number upgrade management of the fare query system is implemented. Furthermore, in this embodiment, please refer to Figure 4 In step S301, the change in configuration data refers to the upgrade and management of the configuration data version number of the fare query system when the configuration data version number changes. The specific implementation steps include: Step S301-1: Read the old version number of the configuration data, load the old version configuration data and generate a snapshot, and import the old version configuration data into the local backup file based on the generated snapshot; Step S301-2: Read the new version number and create a new version configuration node, and import the configuration data from the local backup file into the new version configuration node; Step S301-3: Modify the new version configuration data through the configuration center interactive commands to complete the version number upgrade management of the configuration data.

[0034] Step S302: When the configuration data changes, the configuration data migration management of the fare query system is implemented during configuration data migration. Furthermore, in this embodiment, please refer to Figure 5 In step S302, the change in configuration data refers to the configuration data migration management of the fare query system during configuration data migration. The specific implementation process includes: Step S302-1: The configuration center client loads and finds the version number of the configuration data to be migrated and the corresponding configuration data according to the configuration data migration command, and exports the configuration data to be migrated to the configuration data backup file; Step S302-2: Load the new data source configuration and create a corresponding version number configuration cache node in the new data source; Step S302-3: Import the configuration data from the configuration data backup file into the cache node configured with the version number corresponding to the new data source to complete the configuration migration.

[0035] Step S303: When the configuration data changes, such as during hot updates and version rollbacks, the configuration data of the fare query system is managed for hot updates and version rollbacks.

[0036] Furthermore, in step S303, the changes in configuration data occur when configuration data is hot-updated, i.e., when a certain piece of configuration data is modified, causing this piece of configuration data to change. At this time, the configuration center monitoring task will detect this change, read the change information and hand it over to the configuration center data management module. The configuration center data management module will update this configuration data and reorganize the cached configuration data according to the rules. The changes in configuration data also occur when the configuration data version number is rolled back. A certain old version number is specified through virtual machine parameters and passed to the configuration center service management module. The configuration center service management module loads the old version configuration data according to the old version number, completing the configuration data version rollback to the historical version operation.

[0037] Experimental Example 2: To better understand the technical solution of this application, this application uses the ZooKeeper distributed storage system as the data source, storing configuration data and corresponding version numbers. It uses SSA (Shop Service API, fare search service platform) as the system service proxy, i.e., the fare query system. The application demonstrates the configuration center management method of the fare query system through examples of hot updates of configuration data during SSA service operation, and configuration version number upgrades and rollbacks during service upgrades. The details are as follows: First, start the server and configure data initialization; Furthermore, the server startup and configuration data initialization specifically include: When SSA starts, it transmits the location information of the configuration file in the ZooKeeper configuration storage system and the configuration version number to the configuration center data management module through virtual machine parameters. The configuration center data management module reads the configuration file and loads the address, username, password, and configuration path data according to the data type. The configuration center data management module initializes each service instance and creates a ZooKeeper configuration storage system connection client through the client factory class. It passes the ZooKeeper address, username, password, connects to ZooKeeper, locates the configuration storage path according to the configuration path identifier and version number, creates a snapshot of the path, and listens for changes in all data under the path. Furthermore, the client factory class is used to construct different data source connection instances.

[0038] The configuration center data management module loads all configuration data through snapshots, organizes the configuration data according to the rule of overriding cluster configuration with machine configuration and overriding default configuration with cluster configuration, and stores the organized configuration data in the configuration center data management module cache.

[0039] Furthermore, when SSA calls the interface to read a certain configuration, the corresponding configuration data is provided to SSA; when SSA calls the subscription interface to subscribe to a certain configuration, when this configuration data changes in ZooKeeper, it will be detected by the listening task and updated in the configuration center data management module cache. The updated data is notified to SSA by calling the subscription function provided by SSA.

[0040] Secondly, configuration data is hot-updated during service operation; Furthermore, during SSA runtime, if a configuration item is modified, causing a change in that configuration data, the configuration center data management module will detect this change, read the change information, and hand it over to the configuration center data management module service. The configuration center data management module will update this configuration and reorganize the cached data according to the rules. If this data needs to be updated (not overridden by a higher priority configuration and subscribed to by the SSA service), the SSA service will be notified to update the configuration data through a callback subscription function.

[0041] Then, configure the data version number to upgrade; Furthermore, when an SSA version upgrade occurs, the configuration data version number must also be upgraded to match the SSA service version number; the upgrade process is as follows: The configuration center data management module reads the data source information and old version number information, loads all old version configuration data into the cache of the configuration center data management module, and after loading is complete, exports all configuration data to the backup file. Read the new version number information, create a new version number node under the zookeeper configuration path, and import the full configuration data from the backup file; After importing, users can modify the new version configuration data through command interaction mode or batch scripts to complete the configuration data version number upgrade.

[0042] Finally, the configuration data version number is rolled back.

[0043] Furthermore, when the SSA service starts, it specifies an old version number through virtual machine parameters and passes it to the configuration center data management module. The configuration center data management module loads the old version configuration data according to the old version number and completes the rollback operation of the configuration data version to the historical version.

[0044] Example 3: In this embodiment, a configuration center management system for a fare inquiry system is provided, the configuration center management system comprising: The configuration center service management module is used to initialize the service instances of the clients in the configuration storage system according to the data source configuration file, and to configure the client operations that connect to various data sources through the adapter, and to obtain the configuration data and version number of the data source. The configuration center data management module is used to receive and store configuration data from the configuration center service management module; The configuration center task scheduling module is used to create configuration data listening tasks in the configuration storage system, listen for changes in configuration data, and synchronize the new configuration data to the configuration center data management module. The configuration center command interaction interpreter is used to parse user-input commands and enable the fare query system to call configuration data.

[0045] Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A configuration center management method for a fare inquiry system, characterized in that, The configuration center management method includes: The configuration center service management module initializes each service instance of the client in the configuration storage system according to the data source configuration file, and configures the client operations that connect to various data sources through the adapter to obtain the configuration data and version number of the data source. Based on the version number information of the configuration data, the configuration center service management module loads the configuration data from the storage system into the configuration center data management module. Simultaneously, the configuration center task scheduling module creates a configuration data listening task in the configuration storage system, specifically including: The configuration center service management module reads the version number of the configuration data passed by the virtual machine parameters, and locates the configuration data storage path according to the configuration path parameters and the version number to obtain the corresponding configuration data; Based on the configuration data, the configuration center service management module generates a snapshot on the configuration node of the corresponding version of the configuration data in the storage system, configures the cache node of the corresponding version of the configuration data according to the snapshot, and loads the full configuration data to the cache node. At the same time, the configuration center task scheduling module creates a listening task to listen to the configuration data under the corresponding cache node. The configuration center data management module merges and caches the data under the cache nodes according to the service identifier and merging rules, and loads it into the configuration center data management module; the service identifier includes IP and machine name; the merging rules refer to the following: for configuration data of the same module and the same attribute, cluster configuration data overwrites default configuration data, and single-point configuration data overwrites cluster configuration data; The configuration center command interaction interpreter parses the user-input commands, enabling the fare query system to call configuration data. During the call process, the configuration center task scheduling module monitors changes in configuration data in the configuration storage system and synchronizes the new configuration data to the configuration center data management module, thereby realizing configuration center management of the fare query system. Among them, single-point configuration data is parameter data configured for a single service instance; cluster configuration data is parameter data configured for multiple service instances in a cluster; default configuration data is fallback configuration parameter data used when no corresponding configuration is set in either the cluster or single-point configuration data.

2. The configuration center management method for a fare inquiry system as described in claim 1, characterized in that, The command interaction interpreter in the configuration center parses the user-input commands, enabling the fare query system to access configuration data. During this process, the configuration center task scheduling module monitors changes in the configuration data in the configuration storage system and synchronizes the updated configuration data to the configuration center data management module, thereby enabling configuration center management of the fare query system. The changes in configuration data in the configuration storage system include hot updates, migrations, version number upgrades, and version number rollbacks. The fare query system uses the configuration center command interaction interpreter to retrieve configuration data. Specifically, the configuration center command interaction interpreter enters command interaction mode by starting parameters, including: Enter the command interaction mode by starting the parameters, and then enter the command parameters in the command interaction window; The configuration center command interaction interpreter parses the command parameters, and after parsing, determines whether to exit execution. If execution does not exit, the configuration operation of the corresponding command will be executed and the execution result notification will be returned. If execution exits, the interactive mode will be exited.

3. The configuration center management method for a fare inquiry system as described in claim 2, characterized in that, The configuration center task scheduling module monitors changes in configuration data in the configuration storage system and synchronizes the updated configuration data to the configuration center data management module, thereby enabling configuration center management of the fare query system, including: The configuration data changes when the configuration data version number is upgraded, thus enabling the management of configuration data version number upgrades in the fare query system. Changes in configuration data are addressed during configuration data migration, enabling configuration data migration management for the fare query system. The configuration data changes when there are hot updates or version number rollbacks, enabling the management of hot updates and version number rollbacks for the fare query system.

4. The configuration center management method for a fare inquiry system as described in claim 3, characterized in that, The changes in the configuration data refer to the upgrade and management of the configuration data version number of the fare query system when the configuration data version number changes. Specifically, this includes: Read the old version number of the configuration data, load the old version configuration data and generate a snapshot, and import the old version configuration data into the local backup file based on the generated snapshot; Read the new version number and create a new version configuration node, then import the configuration data from the local backup file into the new version configuration node; Modify the new version configuration data through interactive commands in the configuration center to complete the version number upgrade management of configuration data.

5. The configuration center management method for a fare inquiry system as described in claim 3, characterized in that, The changes in the configuration data refer to the configuration data migration management of the fare query system during configuration data migration, specifically including: The configuration center client loads and finds the version number of the configuration data to be migrated and the corresponding configuration data according to the configuration data migration command, and exports the configuration data to be migrated to the configuration data backup file. Load the new data source configuration and create a corresponding version number configuration cache node in the new data source; Import the configuration data from the configuration data backup file into the cache node configured with the version number corresponding to the new data source to complete the configuration migration.

6. The configuration center management method for a fare inquiry system as described in claim 3, characterized in that: The configuration data changes when a certain configuration data item changes during a hot update. At this time, the configuration center listening task will detect this change, read the change information and hand it over to the configuration center data management module. The configuration center data management module will update this configuration data and reorganize the cached configuration data according to the rules. The configuration data changes when the configuration data version number is rolled back. A certain old version number is specified through virtual machine parameters and passed to the configuration center service management module. The configuration center service management module loads the old version configuration data according to the old version number and completes the configuration data version rollback to the historical version operation.

7. A configuration center management system for a fare inquiry system, used to execute the method as described in any one of claims 1-6, characterized in that, The configuration center management system includes: The configuration center service management module is used to initialize the service instances of the clients in the configuration storage system according to the data source configuration file, and to configure the client operations that connect to various data sources through the adapter, and to obtain the configuration data and version number of the data source. The configuration center data management module is used to receive configuration data loaded from the configuration storage system by the configuration center service management module, complete the merging and caching of the configuration data, and support the fare query system to call the configuration data. The configuration center task scheduling module is used to create configuration data listening tasks in the configuration storage system, listen for changes in configuration data, and synchronize the new configuration data to the configuration center data management module. The configuration center command interaction interpreter is used to parse user-input commands and enable the fare query system to call configuration data.

Images