Visual display method and device for synchronous data

Abstract

The invention provides a visual display method and device for synchronous data, and the method comprises the steps: responding to a received cache query request which is triggered in a first cache query page and aims at at least one business unit in a distributed business system, calling a synchronization server side, and carrying out the synchronization of the at least one business unit through the synchronization server side, obtaining version information of at least one parameter version cached in a local memory of at least one service unit; wherein the version information of at least one parameter version cached in the local memory of each service unit is received by the synchronization server from the parameter management end and synchronized to the service unit; and displaying the version information of the at least one parameter version on the first cache query page. Therefore, the version information of the parameter version cached in the local memory of at least one service unit can be visually displayed, so that a user can conveniently manage the parameter version cached in the local memory of the service unit based on the displayed version information.

Description

Technical Field

[0001] The present application relates to the technical field of data synchronization and information display, and in particular to a method and device for visualizing display of synchronized data. Background Art

[0002] With the development of technology, the centralized business system has gradually been transformed into a distributed one, and the centralized business system has been split into many small business units to handle business. When each business unit processes business, it needs to use pre-configured business parameters, where business parameters can be understood as a kind of system configuration, which define some key values, rules and conditions in the business process, such as product definition, fee structure, interest rate, transaction limit, account type, etc. Among them, the business parameters required by each business unit for business processing can be stored in the local memory of the business unit, but the data stored in the local memory is invisible to the user, which is not conducive to the management of business parameters. Summary of the invention

[0003] The present application proposes a method and device for visual display of synchronized data.

[0004] On the one hand, an embodiment of the present application proposes a method for visual display of synchronized data, the method comprising: in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, calling a synchronization server to obtain, through the synchronization server, version information of at least one parameter version cached in the local memory of the at least one business unit; wherein the version information of at least one parameter version cached in the local memory of each of the business units is received by the synchronization server from a parameter management end and synchronized to the business unit; and the version information of the at least one parameter version is displayed on the first cache query page.

[0005] On the other hand, an embodiment of the present application proposes a visual display device for synchronized data, the device comprising: an acquisition module, for calling a synchronization server in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, so as to obtain version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server; wherein the version information of at least one parameter version cached in the local memory of each of the business units is received by the synchronization server from the parameter management end and synchronized to the business unit; and a display module, for displaying the version information of the at least one parameter version on the first cache query page.

[0006] Another aspect of the present application provides an electronic device, including: a memory and a processor; the memory stores computer instructions, and when the computer instructions are executed by the processor, the method for visual display of synchronized data in the first aspect of the present application is implemented.

[0007] Another aspect of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for visually displaying synchronized data in the first aspect of the present application is implemented.

[0008] According to the method for visual display of synchronized data provided in an embodiment of the present application, in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, a synchronization server is called to obtain version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server, wherein the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit, and the version information of the at least one parameter version is displayed on the first cache query page. This can realize a visual display of the version information of the parameter version cached in the local memory of at least one business unit, thereby facilitating the user to manage the parameter version cached in the local memory of the business unit based on the displayed version information.

[0009] Other effects of the above optional manner will be described below in conjunction with specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present application.

[0011] Figure 1 A schematic diagram of the structure of a data synchronization system provided in one embodiment of the present application;

[0012] Figure 2 A structural diagram of a data synchronization system provided by another embodiment of the present application;

[0013] Figure 3 A schematic diagram of a flow chart of a method for visually displaying synchronized data provided in an embodiment of the present application;

[0014] Figure 4 An example diagram of a first cache query page provided in an embodiment of the present application;

[0015] Figure 5 A schematic diagram of a flow chart of a method for visually displaying synchronized data provided by another embodiment of the present application;

[0016] Figure 6An example diagram of a first pop-up window displayed on a first cache query page provided in an embodiment of the present application;

[0017] Figure 7 An example diagram of a second pop-up window displayed on a first cache query page provided in an embodiment of the present application;

[0018] Figure 8 A schematic diagram of a flow chart of a method for visually displaying synchronized data provided by another embodiment of the present application;

[0019] Fig. 9 An example diagram of a second cache query page provided by an embodiment of the present application;

[0020] Fig.10 An example diagram of a third pop-up window displayed on a second cache query page provided in an embodiment of the present application;

[0021] Fig.11 A schematic diagram of a flow chart of a method for visually displaying synchronized data provided by another embodiment of the present application;

[0022] Fig.12 An example diagram of a task query page provided in an embodiment of the present application;

[0023] Fig.13 A details page of a synchronization task provided in an embodiment of the present application;

[0024] Fig.14 This is an example diagram of a first example query page provided by an embodiment of the present application;

[0025] Fig.15 This is an example diagram of a second example query page provided by an embodiment of the present application;

[0026] Fig.16 A schematic diagram of the structure of a visual display device for synchronized data provided by an embodiment of the present application;

[0027] Fig.17 is a block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] Embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0029] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.

[0030] The present application provides a method and device for visually displaying synchronized data.

[0031] The method for visualizing the synchronized data provided in the embodiment of the present application is applied to the control end in the data synchronization system. Figure 1 , a data synchronization system is described.

[0032] Figure 1 A schematic diagram of the structure of a data synchronization system provided in an embodiment of the present application.

[0033] like Figure 1 As shown, the data synchronization system includes a parameter management terminal 101, a synchronization service terminal 102, a distributed business system 103 and a control terminal 104, and the distributed business system 103 includes multiple business units.

[0034] The parameter management terminal 101 is used to maintain the business parameters required for each business unit in the distributed business system to perform business processing.

[0035] The synchronization server 102 is used to synchronize business parameters, which may also be called a cache synchronization server, a data synchronization server, a parameter synchronization server or other, and this application does not limit this. The synchronization server 102 may be a terminal device or a server, etc. The terminal device may be, for example, a computer, a tablet computer, a personal digital assistant, or other hardware device with various operating systems, touch screens, and / or display screens. This embodiment of the application does not specifically limit the synchronization server.

[0036] Each business unit in the distributed business system 103 can cooperate with other business units to process business based on the business parameters maintained by the parameter management end. For example, the distributed business system can be a distributed banking business system, which includes multiple business units, and each business unit can cooperate with other business units to process user transaction business based on the business parameters maintained by the parameter management end.

[0037] The control terminal 104 is used for visual display of data. The control terminal can be a terminal device or server with a display screen, and the terminal device can be, for example, a computer, a tablet computer, a personal digital assistant, or other hardware device with various operating systems, a touch screen, and / or a display screen. The embodiment of the present application does not specifically limit the control terminal.

[0038] In the embodiment of the present application, each time the parameter management end 101 updates the business parameters, a new parameter version including the updated parameters is generated, and the parameter version is sent to the synchronization server 102. The synchronization server 102 can save the parameter version received from the parameter management end 101 each time in a preset location and synchronize it to each business unit. Thus, each business unit can cache at least one parameter version of the parameter version synchronized by the synchronization server 102 in the local memory.

[0039] Each parameter version may specifically include a parameter table, including updated parameters obtained by updating the service parameters, and the parameter table has a corresponding version identifier, which is used to uniquely identify the version corresponding to the parameter table. The version identifier may be, for example, a version number or other, which is not limited in this application.

[0040] Among them, updating the business parameters once may include deleting one or more business parameters, adding one or more business parameters, modifying one or more business parameters (such as modifying the field name and / or field value of the business parameters), etc., and this application does not limit this. In addition, the business parameters updated by the parameter management end at different times may be the same business parameters or different business parameters. For example, business parameters A and business parameters B may be modified in the last time, and business parameters B and business parameters C may be modified in the next time. This application does not limit this.

[0041] Among all the business parameters required for business processing of multiple business units, if some business parameters are modified, one parameter version may include the unmodified business parameters and the updated parameters corresponding to the modified business parameters, or it may only include the updated parameters corresponding to the modified business parameters. This application does not impose any restrictions on this.

[0042] Among them, a SDK (Software Development Kit) can be deployed in the parameter management end 101, and each parameter version obtained by the parameter management end 101 can be sent by the SDK to the synchronization service end 102. Among them, in order to distinguish it from other SDKs, the SDK deployed in the parameter management end 101 can be called a second SDK, or it can also be called a cache synchronization SDK or others, and this application does not limit this.

[0043] The following describes how the synchronization service end 102 synchronizes the parameter version received from the parameter management end 101 to each business unit.

[0044] Specifically, each time the synchronization server 102 receives a parameter version sent by the parameter management end, the parameter version can be saved in a preset position. After saving, the parameter version is ready in the synchronization server 102, so that it can wait for each business unit to pull it. Correspondingly, the parameter version received by the synchronization server from the parameter management end can be one or more. Each business unit in the distributed business system 103 can continuously send a heartbeat request to the synchronization server 102 to detect whether the latest parameter version of at least one parameter version received by the synchronization server 102 from the parameter management end 101 has been saved in a preset position and has not been synchronized to any business unit. Among them, the sending interval of the heartbeat request can be set as needed, and this application does not impose any restrictions on this. Among them, the latest parameter version is the parameter version that the synchronization server 102 received from the parameter management end 101 the most recent time. Among them, the latest parameter version is not synchronized to any business unit, which can be understood as the latest parameter version has not been synchronized to any business unit before the current moment.

[0045] When any business unit detects that the latest parameter version has been saved in a preset location, it can determine that the latest parameter version has been prepared in the synchronization server 102 and is waiting to be pulled to the any business unit, and when it detects that the latest parameter version has not been synchronized to the any business unit, it sends a first data synchronization request to the synchronization server 102. The first data synchronization request can carry the version information of the latest parameter version, so that the synchronization server 102 can send the target parameter version including the latest parameter version to the any business unit based on the version information.

[0046] The version information of any parameter version may include information for uniquely identifying the parameter version, such as a version number corresponding to the parameter version, etc. The version number may follow a certain naming convention, such as the version number of the parameter version obtained by modifying the business parameters for the first time is 1, the version number of the parameter version obtained by modifying the business parameters for the second time is 2, and the version numbers of the parameter versions obtained by other modifications are similar.

[0047] The target parameter version may include the latest parameter version received by the synchronization server 102 from the parameter management terminal 101 and at least one parameter version received before the latest parameter version. For example, the target parameter version may include the latest parameter version and the next latest parameter version received by the synchronization server 102 from the parameter management terminal 101; or, the target parameter version may only include the latest parameter version, which is not limited in this application. The next latest parameter version refers to the parameter version received by the synchronization server 102 before receiving the latest parameter version.

[0048] The synchronization service end 102 synchronizes the latest parameter version and the next latest parameter version received from the parameter management end 101 to any business unit. When the arbitrary business unit receives a task to be processed, but the next latest parameter version has been synchronized but the latest parameter version has not been synchronized, the arbitrary business unit can temporarily use the next latest parameter version to process the business.

[0049] After any business unit receives the target parameter version synchronized by the synchronization server 102, it can save the target parameter version in the cache area of ​​the local memory of the arbitrary business unit, so that the arbitrary business unit can quickly read it from the cache area of ​​the local memory when it needs to use the parameter version without going through the network, thereby reducing the time consumption of parameter reading.

[0050] As an example, the preset location includes the database and local memory of the synchronization server 102. Among them, in order to avoid the loss of the stored parameter version after the synchronization server 102 crashes and restarts, the synchronization server 102 can store the parameter version received each time in the database of the synchronization server 102, that is, the database of the synchronization server 102 can store all parameter versions received from the parameter management end 101. In order to save the storage space of the local memory of the synchronization server 102, the local memory of the synchronization server 102 can only store the N parameter versions that the synchronization server 102 has recently received from the parameter management end 101, where N is an integer greater than or equal to 1. Among them, the N parameter versions that the synchronization server 102 has recently received from the parameter management end 101, that is, the most recent and the N-1 times before the most recent, are the parameter versions received from the parameter management end 101.

[0051] Correspondingly, any business unit can determine whether the latest parameter version has been saved in the database by detecting whether the latest parameter version is included in all parameter versions stored in the database of the synchronization server 102, and determine whether the latest parameter version has been saved in the local memory of the synchronization server 102 by detecting whether the latest parameter version is included in the N parameter versions stored in the local memory of the synchronization server 102.

[0052] In the case where all parameter versions stored in the database of the synchronization server 102 include the latest parameter version, it can be determined that the latest parameter version has been stored in the database, and in the case where the N parameter versions stored in the local memory of the synchronization server 102 include the latest parameter version, it can be determined that the latest parameter version has been stored in the local memory of the synchronization server 102. In the case where any business unit detects that the latest parameter version has been stored in the database and local memory of the synchronization server 102, it can be determined that the latest parameter version is ready and waiting to be pulled to the any business unit.

[0053] It should be noted that, as an example, the synchronization server 102 can save the parameter version received from the parameter management terminal 101 each time in the database first, and then save it in the local memory. Then, any business unit can directly read the data stored in the local memory of the synchronization server 102 to detect whether the N parameter versions stored in the local memory include the latest parameter version. If so, it is determined that the latest parameter version has been saved in the database and local memory of the synchronization server 102. By directly reading the data stored in the local memory of the synchronization server 102 to detect whether the latest parameter version has been saved in the database and local memory of the synchronization server 102, the detection efficiency is improved.

[0054] As an example, the heartbeat request sent by any business unit to the synchronization server 102 carries the corresponding timestamp information, which indicates the time when the parameter version synchronized by the synchronization server 102 was last received; accordingly, any business unit can determine whether the latest parameter version has been synchronized to the any business unit by detecting whether the saving time of the latest parameter version at the preset position is before the time corresponding to the timestamp information. Among them, the latest parameter version has been synchronized to any business unit, which can be understood as the latest parameter version has been synchronized to the any business unit before the current time. Among them, when the latest parameter version is saved at the preset position before the time corresponding to the timestamp information carried by the heartbeat request, it means that the latest parameter version has been synchronized to the arbitrary business unit at the latest at the time corresponding to the timestamp information, so that it can be determined that the latest parameter version is synchronized to the arbitrary business unit at the current moment; when the latest parameter version is saved at the preset position not before the time corresponding to the timestamp information carried by the heartbeat request, it means that the latest parameter version is saved at the preset position at the same time or after the time corresponding to the timestamp information, and at the time corresponding to the timestamp information, the latest parameter version has not been prepared or has not been received from the parameter management end, so it has not been synchronized to the arbitrary business unit at the time corresponding to the timestamp information, so it can be determined that the latest parameter version has not been synchronized to the arbitrary business unit at the current moment.

[0055] It should be noted that, when the preset location includes the database and local memory of the synchronization server 102, the latest parameter version can be considered to be ready on the synchronization server and waiting to be pulled to any business unit only when the latest parameter version has been saved in the database and the local memory. The synchronization server 102 can save the parameter version received from the parameter management end each time in the database first, and then save it in the local memory. Then, any business unit can detect whether the saving time of the latest parameter version in the local memory is before the time corresponding to the timestamp information carried by the heartbeat request. If the saving time is before the time corresponding to the timestamp information carried by the heartbeat request, it means that the latest parameter version has been synchronized to the any business unit at the latest at the time corresponding to the timestamp information, so that it can be determined that the latest parameter version has been synchronized to the any business unit at the current time; if the saving time is not before the time corresponding to the timestamp information carried by the heartbeat request, it means that the latest parameter version is saved in the local memory of the synchronization server 102 at the same time or after the time corresponding to the timestamp information, and at the time corresponding to the timestamp information, the latest parameter version has not been prepared or has not been received from the parameter management end 101, so it has not been synchronized to the any business unit at the time corresponding to the timestamp information, so it can be determined that the latest parameter version has not been synchronized to the any business unit at the current time.

[0056] Therefore, based on the timestamp information carried in the heartbeat request sent by any business unit, it is possible to accurately detect whether the latest parameter version has been synchronized to any business unit.

[0057] As an example, the heartbeat request sent by any business unit to the synchronization server 102 carries the corresponding historical version information, wherein the historical version information indicates the version information of the parameter version that has been synchronized to any business unit; accordingly, any business unit can determine whether the latest parameter version has been synchronized to the any business unit by detecting whether the parameter version corresponding to the historical version information includes the latest parameter version. Wherein, if the parameter version corresponding to the historical version information includes the latest parameter version, it is determined that the latest parameter version has been synchronized to the any business unit; if the parameter version corresponding to the historical version information does not include the latest parameter version, it is determined that the latest parameter version has not been synchronized to the any business unit.

[0058] Therefore, based on the historical version information carried in the heartbeat request sent by any business unit, it is possible to accurately detect whether the latest parameter version has been synchronized to any business unit.

[0059] As an example, any parameter version sent by the parameter management terminal 101 to the synchronization service terminal 102 has corresponding storage indication information, wherein the storage indication information is used to indicate the storage type of the corresponding parameter version. The storage type can be set as needed, and may include a memory type, a database type, and the like. For example, when the amount of data of a certain parameter version is large, the storage type corresponding to the parameter version may be set to a database type; when the amount of data of a certain parameter version is small, the storage type corresponding to the parameter version may be set to a memory type. For example, the storage indication information may include "1", indicating that the storage type of the corresponding parameter version is a memory type, or the storage indication information may include "0", indicating that the storage type of the corresponding parameter version is a database type. The storage type and storage indication information corresponding to any parameter version may be set on the parameter management terminal 101, and sent to the synchronization service terminal 102 together with the parameter version.

[0060] When the synchronization server 102 synchronizes the target parameter version to any business unit, the storage indication information corresponding to each parameter version in the target parameter version can also be synchronized to the arbitrary business unit, so that the arbitrary business unit can save the corresponding parameter version in the local memory of the arbitrary business unit when the storage type indicated by the storage indication information is a memory type, and save the corresponding parameter version in the database of the arbitrary business unit when the storage type indicated by the storage indication information is a database type.

[0061] As an example, in order to save storage space, the local memory of any business unit may only store the M most recently saved parameter versions, and the database of any business unit may only store the P most recently saved parameter versions, where M and P are integers greater than or equal to 1.

[0062] Among them, by setting M and P to integers greater than 1, that is, saving at least 2 parameter versions in the local memory and database of any business unit respectively, it is possible to flexibly read the parameter version required for the business to be processed from the local memory and / or database of any business unit according to the needs of the business to be processed, so as to process the business according to the parameter version required by the business to be processed.

[0063] In the case where only the M parameter versions most recently saved in the local memory of any business unit are saved, and only the P parameter versions most recently saved in the database of any business unit are saved, for any business to be processed acquired by the arbitrary business unit, there is a case where the parameter version required by the arbitrary business is not stored in the local memory and database of the arbitrary business unit, then the arbitrary business unit can send a second data synchronization request to the synchronization server, wherein the second data synchronization request carries the version information of the parameter version required by the arbitrary business, so as to obtain the parameter version required by the arbitrary business from the synchronization server 102. That is, in response to acquiring the first business to be processed, the arbitrary business unit can search for the parameter version required by the first business from the local memory and database of the arbitrary business unit, and in the case where the parameter version required by the first business is not included in the local memory and database of the arbitrary business unit, the second data synchronization request can be sent to the synchronization server 102, wherein the second data synchronization request carries the version information of the parameter version required by the first business, so as to obtain the parameter version required by the first business from the synchronization server 102.

[0064] The first business is any business to be processed acquired by any business unit. The parameter version required for the first business can be determined by the first business unit in the distributed business system that executes the business processing flow of the first business. The first business unit in the distributed business system that executes the business processing flow of the first business may be any of the above-mentioned business units in the embodiment of the present application, or may be other business units except the arbitrary business unit.

[0065] For example, assume that the first service is processed by service unit 1 and service unit 2 in the distributed service system. Service unit 1 stores a parameter table with version 8 and a parameter table with version 9 in its local memory, and service unit 2 stores a parameter table with version 7 and a parameter table with version 8 in its local memory.

[0066] Assuming that the first business unit that executes the business processing flow of the first business is business unit 1, and business unit 1 determines that the parameter version required by the first business corresponds to version number 9, it can directly read the parameter table with version number 9 from its local memory to process the first business.

[0067] After obtaining the first service to be processed, the service unit 2 may send a second data synchronization request to the synchronization server, wherein the second data synchronization request carries a version number 9, so as to obtain a parameter table with a version number of 9 from the synchronization server.

[0068] As an example, in order to ensure that multiple business units in the distributed business system 103 that cooperate to process the same business can process the business normally based on the same parameter version, the business unit that first executes the business processing flow of the business in the distributed business system 103 can synchronize the parameter version required for the business to other business units after determining the parameter version required for the business.

[0069] Accordingly, for any business unit in the distributed business system, when the arbitrary business unit processes the second business for the distributed business system, if it is the first business unit in the distributed business system to execute the business processing flow of the second business, the arbitrary business unit can synchronize the target parameter version to other business units in the distributed business system 103 when determining to adopt the target parameter version and execute the business processing flow of the second business. The second business is any business to be processed acquired by any business unit.

[0070] For example, assuming that the business processing flow of the second business is that business unit 1 in the distributed business system first processes part of the second business, and then business unit 2 processes the other part of the business, then business unit 1 is the first business unit to execute the business processing flow of the second business when processing the second business for the distributed business system. In the case where business unit 1 determines to use the parameter table with version number 9 to execute the business processing flow of the second business, business unit 1 can synchronize the parameter table with version number 9 obtained from the synchronization server to business unit 2, so that business unit 1 and business unit 2 can process the second business based on the parameter table with version number 9 to ensure the normal processing of the second business.

[0071] As an example, an SDK can be deployed in any business unit, and the method executed by the any business unit in the above embodiment can be executed through the SDK. In order to distinguish it from other SDKs, the SDK deployed in any business unit can be called the first SDK, or it can also be called a cache query SDK or others, and this application does not limit this.

[0072] Therefore, in the data synchronization system provided by the embodiment of the present application, after the parameter management end updates the business parameters each time to obtain a new parameter version, any business unit can obtain the latest parameter version from the synchronization service end in time and cache it in the local memory, and then directly and quickly read the updated business parameters from the local memory when needed, without going through the network, to ensure the business processing efficiency of the business unit, and, in the case where the parameter management end updates multiple business parameters at a time, the multiple business parameters updated at a time can take effect in the business unit at the same time, and a new parameter version is generated after each update of the business parameters, and the parameters are synchronized based on the parameter version after the update, which is convenient for tracking the change history of the business parameters, making the management of the business parameters more reasonable. And any business unit can save the parameter version synchronized by the synchronization service end in the local memory or database of the arbitrary business unit as needed based on the storage indication information of the parameter version set by the parameter management end. Among them, by saving the parameter version synchronized by the synchronization service end in the local memory of the arbitrary business unit, the arbitrary business unit can quickly read from the local memory when the parameter version is needed, without going through the network, and can further reduce the time consumption of reading business parameters compared to saving in the database of the arbitrary business unit. By saving the parameter version synchronized by the synchronization server in the database of the arbitrary business unit, it is possible to avoid the loss of stored data after the arbitrary business unit crashes and restarts, and save storage space in the local memory.

[0073] In order to more clearly understand the data synchronization system of the present application, further explanation is given below with reference to examples, wherein the distributed business system is a banking business system, and a parameter version includes a parameter table with a corresponding version number.

[0074] like Figure 2 As shown, the data synchronization system may include a parameter management end, a synchronization service end, a distributed business system, and a control end. The distributed business system includes multiple business units. Among them, the parameter management end may include a parameter maintenance unit and a second SDK. The parameter management end has a corresponding database, that is, Figure 2 The synchronization server has a corresponding database, namely Figure 2 The first SDK can be deployed in each business unit, and each business unit has a corresponding database, that is, Figure 2 The business library in .

[0075] When business parameters need to be maintained, the administrator who performs business parameter maintenance can initiate a parameter maintenance request through the unified counter (corresponding to Figure 2 In step 1), the parameter maintenance unit in the parameter management terminal can receive the parameter maintenance request through the gateway (corresponding to Figure 2Step 2) in the above table, and perform parameter maintenance. The unified counter is a platform for processing all business processes of counter services in the banking business system.

[0076] After the parameter maintenance unit updates the service parameters once to obtain a parameter table with a version number, the parameter table of this version can be sent to the parameter center library of the parameter management end for storage (corresponding to Figure 2 Step 3), and send the parameter table of this version to the second SDK deployed in the parameter management terminal (corresponding to Figure 2 Then, the second SDK can send a synchronization task to the synchronization server, where the task information of the synchronization task includes the parameter table of the version (corresponding to Figure 2 After receiving the task information of the synchronization task, the synchronization server can execute the corresponding synchronization task based on the task information, that is, first save the parameter table of the version in the database of the synchronization server, and then save it in the local memory (corresponding to Figure 2 In step 6), wait for each business unit to pull.

[0077] The local memory of the synchronization server can store the N versions of parameter tables recently sent by the parameter management end, where N is 2, for example. The database of the synchronization server can store all versions of parameter tables received from the parameter management end.

[0078] Each business unit can continuously send heartbeat requests to the synchronization server to pull the parameter table from the synchronization server (corresponding to Figure 2 In step 7), any business unit may send a heartbeat request through the first SDK deployed therein, and pull a parameter table from the synchronization server.

[0079] Among them, the process of any business unit pulling the parameter table from the synchronization server can be: any business unit continuously sends heartbeat requests to the synchronization server to detect whether the latest version of the parameter table received by the synchronization server from the parameter management end has been saved in the local memory and database of the synchronization server, and the latest version of the parameter table has not been synchronized to the business unit. In the case that the arbitrary business unit detects that the latest version of the parameter table received by the synchronization server from the parameter management end has been saved in the local memory and database of the synchronization server, it can be determined that the latest version of the parameter table has been prepared on the synchronization server, and when it is detected that the latest version of the parameter table has not been synchronized to the arbitrary business unit, a first data synchronization request is sent to the synchronization server. Among them, the latest version of the parameter table is a version of the parameter table that the synchronization server received from the parameter management end the most recently.

[0080] When the synchronization server receives the first data synchronization request, it can determine the target parameter table that needs to be synchronized to the arbitrary business unit based on the version information of the latest version of the parameter table carried therein, and synchronize it to the arbitrary business unit. The target parameter table synchronized to the arbitrary business unit may include the latest version of the parameter table and the next latest version of the parameter table. After the arbitrary business unit receives the target parameter table synchronized by the synchronization server, it can save the target parameter table in the local memory of the arbitrary business unit.

[0081] When the arbitrary business unit detects based on the heartbeat request that the latest version of the parameter table received by the synchronization server from the parameter management end is not saved in the local memory and database of the synchronization server, that is, the latest version of the parameter table has not been prepared on the synchronization server, or when it is detected that the latest version of the parameter table has been synchronized to the arbitrary business unit, it can continue to send heartbeat requests to the synchronization server to continue the detection.

[0082] In addition, when the parameter maintenance unit sends each version of the parameter table to the second SDK, it can also send the corresponding storage indication information. Accordingly, each version of the parameter table stored in the synchronization server can have the corresponding storage indication information. The synchronization server can send the corresponding storage indication information when sending the target parameter table to any business unit.

[0083] Any business unit receives the target parameter table and corresponding storage indication information (corresponding to the synchronization server) synchronized by the synchronization server. Figure 2 After step 8), if the storage type is determined to be a memory type, the corresponding parameter table can be saved in the local memory of the arbitrary business unit. If the storage type is determined to be a database type, the corresponding parameter table can be saved in the database of the arbitrary business unit (corresponding Figure 2 Step 9).

[0084] Among them, for each synchronization task sent by the second SDK to the synchronization server, after the parameter table included in the task information of the synchronization task is synchronized to any business unit, the synchronization task is deemed to be executed successfully.

[0085] It should be noted that when the second SDK sends multiple synchronization tasks to the synchronization server in a short period of time, there may be a situation where the synchronization server receives a synchronization task but the previous one or several synchronization tasks have not been successfully executed. In order to improve the execution efficiency of synchronization tasks, when the synchronization server receives each synchronization task, it can detect whether the previously received synchronization task, that is, the historical synchronization task, has been successfully executed. If it detects that there are historical synchronization tasks that have not been successfully executed, it can merge the currently received synchronization task with the historical synchronization tasks that have not been successfully executed into one synchronization task for execution. For example, the task information of each synchronization task may include a parameter table with a corresponding version number. Assuming that when the synchronization server receives synchronization task 8 for synchronizing a parameter table with version number 8, it detects that the previously received parameter table with version number 7 and parameter table with version number 6 have not been synchronized to any business unit, then synchronization task 7 for synchronizing the parameter table with version number 7, synchronization task 6 for synchronizing the parameter table with version number 6, and synchronization task 8 for synchronizing the parameter table with version number 8 can be merged into one synchronization task, and the parameter table with version number 6, the parameter table with version number 7, and the parameter table with version number 8 can be stored together in the local memory and database. When the synchronization of these versions of the parameter tables is successful, the merged synchronization task is deemed to be executed successfully.

[0086] In addition, the local memory and database of any business unit can only store the parameter tables stored in the last two times. For any pending business, if the business unit fails to find the parameter table of the required version of the business from its local memory and database, it can send a second data synchronization request to the synchronization server (corresponding to Figure 2 In step 10), the version information of the version required by the service is carried to obtain the parameter table of the version required by the service from the synchronization server.

[0087] In addition, the data synchronization system may also include a user management module for authorizing the user login parameter management terminal and configuring user rights.

[0088] Combine the following Figure 3 , the visualization display method of synchronization data provided in an embodiment of the present application is described. Figure 3 A flowchart of a method for visually displaying synchronized data provided in an embodiment of the present application.

[0089] It should be noted that the method for visual display of synchronized data provided in the embodiment of the present application can be performed by a visual display device for synchronized data. The visual display device for synchronized data can be the control terminal in the above embodiment, or can be configured in the control terminal. The embodiment of the present application is described by taking the visual display device for synchronized data as the control terminal as an example.

[0090] like Figure 3 As shown, the method for visual display of synchronization data provided in the embodiment of the present application may include the following steps:

[0091] Step 301, in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, calls the synchronization server to obtain, through the synchronization server, version information of at least one parameter version cached in the local memory of at least one business unit; wherein, the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit.

[0092] Among them, the first cache query page is a page provided by the management and control end for querying cached data in the local memory of each business unit. Among them, since the SDK can be deployed in the business unit, and the parameter version obtained by updating the business parameters is pulled from the synchronization server, the business unit in the embodiment of the present application can be called a consumer-side instance or a client instance. Correspondingly, the first cache query page can also be called a consumer-side cache query page.

[0093] The at least one business unit is any one or more business units among the multiple business units included in the distributed business system.

[0094] Any parameter version cached in the local memory of any business unit is sent by the parameter management end to the synchronization server, and then synchronized to the parameter version of the business unit through the synchronization server.

[0095] In an embodiment of the present application, the first cache query page may display a button for triggering a cache query request. The cache query request is used to request a query on cached data in the local memory of any one or more business units. The user can trigger a cache query request for at least one business unit in the distributed business system by clicking the button. Thus, in response to receiving the cache query request triggered on the first cache query page, the management and control end can call the synchronization server to obtain the version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server.

[0096] As an example, the first cache query page may include an input box or a selection box for inputting query conditions. The user may input the query conditions in the input box or select the query conditions in the selection box, and click the above button to trigger a cache query request for the business unit that meets the query conditions. The cache query request may carry the query conditions input or selected by the user. In response to receiving the cache query request, the management end may call the synchronization server to determine the business units that meet the query conditions through the synchronization server, and send a query cache request to these business units (specifically, the SDK deployed in the business units). After these business units obtain the version information of at least one parameter version cached in their local memory in response to the received request, they may return the version information to the synchronization server, so that the synchronization server can return the version information to the management end. Among them, the business unit that meets the query conditions is at least one business unit in step 301.

[0097] The query condition may include one or more of the host name of the host where the business unit is located, the IP (Internet Protocol) address, the port number of the monitored port, the business unit name, the namespace, etc. The business unit name is also called the instance name. The namespace is a logical container for organizing and distinguishing identifiers (such as variable names, function names, class names, etc.) to avoid naming conflicts.

[0098] It should be noted that the data synchronization system also includes a registration center. Any business unit in the distributed business system that has SDK deployed and can obtain parameter versions from the synchronization server can register information in the registration center, so that the registration center can save the attribute information of the registered business unit. When the user does not enter or select any query conditions, at least one business unit in step 301 includes all business units in the distributed business system that have registered information in the registration center.

[0099] Step 302: Display version information of at least one parameter version on the first cache query page.

[0100] In an embodiment of the present application, version information of at least one parameter version cached in the local memory of at least one business unit can be displayed in a list page on the first cache query page.

[0101] It should be noted that in the embodiment of the present application, in response to receiving a cache query request for at least one business unit triggered on the first cache query page, the management end may also call the synchronization server to obtain the attribute information of the at least one business unit through the synchronization server, and display the attribute information of the at least one business unit on the first cache query page. In addition, in the case where the parameter version includes a parameter table, the table name of at least one parameter table cached in the local memory of the at least one business unit may also be obtained through the synchronization server, and the table name may be displayed on the first cache query page.

[0102] The attribute information of any business unit may include one or more of the host name, IP address, port number of the monitored port, business unit name, status, etc. of the host where the business unit is located.

[0103] For example, refer to Figure 4 The first cache query page shown on the right may display an input box or selection box for entering query conditions, wherein the query conditions include the host name of the host where the business unit is located, the port number of the listening port, the instance name, and the namespace. The user may select "ParamCerter" in the selection box corresponding to the namespace, and click the "Query" button to trigger a cache query request for business units that meet the query conditions. In response to the cache query request, the management and control end may call the synchronization server to obtain the host name, port number, instance name, table name of the parameter table cached in the local memory, and the corresponding version number of the business unit that meets the query conditions through the synchronization server, and display them on the first cache query page. Among them, Figure 4 The "TEST" in the table is the name of the parameter table.

[0104] It should be noted that the reference Figure 4 For any business unit, when the above information is displayed on the first cache query page, the operations that can be performed on the above information can also be displayed, such as viewing details.

[0105] The method for visual display of synchronized data provided in an embodiment of the present application responds to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, calls a synchronization server, and obtains version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server, wherein the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit, and the version information of the at least one parameter version is displayed on the first cache query page, so as to realize visual display of the version information of the parameter version cached in the local memory of at least one business unit, thereby facilitating the user to manage the parameter version cached in the local memory of the business unit based on the displayed version information.

[0106] It is understandable that, in addition to synchronizing at least one parameter version received from the parameter management end to the business unit, the synchronization server also caches at least one parameter version of all parameter versions received from the parameter management end in the local memory of the synchronization server. In order to facilitate the comparison of the version information of the business unit and the parameter version cached in the local memory of the synchronization server, the management and control end can also provide a version verification function. Figure 5 , the visualization display method of synchronization data provided in the embodiment of the present application is further explained.

[0107] Figure 5 A schematic flow chart of a method for visually displaying synchronized data provided in another embodiment of the present application.

[0108] like Figure 5 As shown, the method for visually displaying synchronization data may include the following steps:

[0109] Step 501, in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, calls a synchronization server to obtain, through the synchronization server, version information of at least one parameter version cached in a local memory of at least one business unit, wherein the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit.

[0110] Step 502: Displaying version information of at least one parameter version cached in the local memory of at least one business unit on a first cache query page.

[0111] Step 503, in response to receiving a version verification request for the first business unit in at least one business unit triggered on the first cache query page, obtain the version information of at least one parameter version cached in the local memory of the first business unit, and call the synchronization server to obtain the version information of at least one parameter version cached in its local memory through the synchronization server.

[0112] The at least one business unit in step 503 may be the same business unit as the at least one business unit in steps 501 and 502. The first business unit is any one or more business units in the at least one business unit.

[0113] In an embodiment of the present application, when the version information of at least one parameter version in the local memory of at least one business unit is displayed on the first cache query page, the selection boxes corresponding to each business unit may be displayed accordingly, and the user may select the corresponding first business unit through the selection boxes corresponding to any one or more of the business units. In addition, a button for triggering a version verification request may be displayed on the first cache query page. Among them, the version verification request is used to request a comparison of the version information of the parameter version cached in the local memory of any one or more business units with the synchronization server. After the user selects the first business unit and clicks the button, a version verification request for the first business unit may be triggered. Thus, the management and control end can obtain the version information of at least one parameter version in the local memory of the first business unit from the version information of the parameter version that has been obtained, and call the synchronization server to obtain the version information of at least one parameter version cached in its local memory through the synchronization server.

[0114] Step 504, displaying a first pop-up window on the first cache query page, the first pop-up window including version information of at least one parameter version cached in the local memory of the synchronization server, and version information of at least one parameter version cached in the local memory of the first business unit.

[0115] Among them, the steps in steps 501-504 that are similar to other embodiments can refer to other embodiments and are not described in detail here.

[0116] As an example, in order to distinguish different business units, the attribute information of the first business unit can also be displayed in the first pop-up window, wherein the attribute information can include one or more of the host name, IP address, port number of the monitored port, business unit name, status, etc. of the host where the first business unit is located.

[0117] For example, the user can select Figure 4In the example above, select the business unit with the host name Localhost and click the "Version Check" button to trigger a version check request for the business unit. In response to the version check request, the management end can obtain the version information of at least one parameter version in the local memory of the business unit, and call the synchronization server to obtain the version information of at least one parameter version cached in the local memory of the synchronization server through the synchronization server, and display the version information. Figure 6 The first pop-up window shown. Figure 6 The "16,17" corresponding to the "consumer version" is the version information of the parameter version cached in the local memory of the business unit, and the "16,17" corresponding to the "server version" is the version information of the parameter version cached in the local memory of the synchronization server.

[0118] Therefore, through the version verification function provided by the management and control end, the version information of at least one parameter version cached in the local memory of the synchronization server and the version information of at least one parameter version cached in the local memory of the first business unit can be displayed simultaneously, so as to facilitate the user to compare the version information of the parameter versions cached in the local memory of the first business unit and the synchronization server, and then facilitate the user to manage the parameter versions cached in the local memory of the first business unit.

[0119] As an example, all parameter versions received by the synchronization server from the parameter management end are stored in the database of the synchronization server. The version verification function provided by the management end can also be used to compare the version information of the parameter versions in the local memory of the business unit and the synchronization server and in the database of the synchronization server. Correspondingly, the visual management method of synchronization data provided in the embodiment of the present application can also include:

[0120] In response to receiving a version verification request for the first business unit in at least one business unit triggered on the first cache query page, the synchronization server is called to obtain the version information of all parameter versions stored in its database through the synchronization server; accordingly, the first pop-up window also includes the version information of all parameter versions stored in the database of the synchronization server.

[0121] Correspondingly, the version check request is used to request a comparison of the version information of the parameter version in the local memory of any one or more business units and the local memory of the synchronization server and the database of the synchronization server.

[0122] Therefore, through the version verification function provided by the management and control end, the version information of at least one parameter version cached in the local memory of the first business unit, the version information of at least one parameter version cached in the local memory of the synchronization server, and the version information of all parameter versions stored in the database of the synchronization server can be displayed simultaneously, thereby facilitating users to compare the version information of the parameter versions in the local memory of the first business unit and the synchronization server and in the database of the synchronization server, and further facilitating users to manage the parameter versions cached in the local memory of the first business unit.

[0123] As an example, the management and control end also provides a memory usage query function for any one or more business units. Accordingly, in the visualization management method of synchronized data provided in the embodiment of the present application, it may also include:

[0124] In response to receiving a memory occupancy query request for a second business unit in at least one business unit triggered on the first cache query page, calling a synchronization server to obtain memory occupancy information of cached data in a local memory of the second business unit through the synchronization server;

[0125] A second pop-up window is displayed on the first cache query page, and the second pop-up window includes memory usage information of cache data in the local memory of the second business unit.

[0126] The memory usage information of the cached data may include information such as the memory usage size of the cached data and the memory usage size of index data corresponding to the cached data.

[0127] The at least one business unit here may be the same business unit as the at least one business unit referred to in steps 501 and 502. The second business unit is any one or more business units in the at least one business unit.

[0128] In an embodiment of the present application, when the version information of at least one parameter version in the local memory of at least one business unit is displayed on the first cache query page, the selection box corresponding to each business unit can be displayed accordingly, and the user can select the corresponding second business unit through the selection box corresponding to any one or more business units. In addition, a button for triggering a memory occupancy query request can be displayed on the first cache query page. Among them, the memory occupancy query request is used to request to query the memory occupancy of cached data in the local memory of any one or more business units. After the user selects the second business unit and clicks the button, a memory occupancy query request for the second business unit can be triggered. Thus, the management end can call the synchronization server to obtain the memory occupancy information of the cached data in the local memory of the second business unit through the synchronization server. Among them, the memory occupancy query request can carry the identification information of the second business unit, and the synchronization server can send a request for querying the memory occupancy to the corresponding second business unit based on the identification information of the second business unit. In response to the request, the second business unit can return the memory occupancy information of the cached data in the local memory to the synchronization server, so that the synchronization server can return the memory occupancy information of the second business unit to the management end.

[0129] As an example, in order to distinguish different business units, the attribute information of the second business unit can also be displayed in the second pop-up window, wherein the attribute information can include one or more of the host name, IP address, port number of the monitored port, business unit name, status, etc. of the host where the second business unit is located.

[0130] For example, the user can select Figure 4 In the example above, select the business unit with the host name Localhost and click the "View Occupied Memory" button to trigger a memory usage query request for the business unit. In response to the memory usage query request, the management end can call the synchronization server to obtain the memory usage information of the cached data in the local memory of the second business unit through the synchronization server and display it. Figure 7 The second pop-up window shown. Figure 7 The "646B" corresponding to the "Cache Data Size" refers to the memory usage of the cache data in the local memory of the business unit, and the "0B" corresponding to the "Index Data Size" refers to the memory usage of the index data corresponding to the cache data in the local memory of the business unit.

[0131] Therefore, through the memory usage query function provided by the management and control end, the memory usage information of the cached data in the local memory of the second business unit can be displayed, so that the user can understand the size of the available space in the local memory of the second business unit, and then the user can manage the parameter version cached in the local memory of the second business unit.

[0132] As an example, the control end also provides a cache data verification function. Accordingly, in the visualization management method of synchronized data provided in the embodiment of the present application, it may also include:

[0133] In response to receiving a data verification request for a fourth business unit in the at least one business unit triggered on the first cache query page, calling the synchronization server to obtain, through the synchronization server, data information in at least one parameter version cached in a local memory of the synchronization server, and data information in at least one parameter version cached in a local memory of the fourth business unit;

[0134] A fourth pop-up window is displayed on the first cache query page, and the fourth pop-up window includes data information in at least one parameter version cached in the local memory of the synchronization server and data information in at least one parameter version cached in the local memory of the fourth business unit.

[0135] The at least one business unit here may be the same business unit as the at least one business unit referred to in steps 501 and 502. The fourth business unit is any one or more business units in the at least one business unit.

[0136] The data information of any parameter version may include updated parameters included in the parameter version.

[0137] In an embodiment of the present application, when the version information of at least one parameter version in the local memory of at least one business unit is displayed on the first cache query page, the selection boxes corresponding to each business unit can be displayed accordingly, and the user can select the corresponding fourth business unit through the selection boxes corresponding to any one or more business units. In addition, a button for triggering a data verification request can be displayed on the first cache query page. Among them, the data verification request is used to request a comparison of the data information in the parameter version cached in the local memory of any one or more business units and the synchronization server. After the user selects the fourth business unit and clicks the button, a data verification request for the fourth business unit can be triggered. Thus, the management and control end can call the synchronization server to obtain the data information in at least one parameter version cached in the local memory of the synchronization server through the synchronization server, and obtain the data information in at least one parameter version cached in the local memory of the fourth business unit, and then display the fourth pop-up window including this information on the first cache query page.

[0138] Therefore, through the data verification function provided by the management and control end, the data information in at least one parameter version cached in the local memory of the synchronization server and the fourth business unit can be displayed at the same time, so as to facilitate the user to compare the data information in the parameter version cached in the local memory of the fourth business unit and the synchronization server, and then facilitate the user to manage the parameter version cached in the local memory of the fourth business unit.

[0139] From the above analysis, it can be seen that the control end can visualize the cached data in the local memory of the business unit. In one implementation, the control end can also visualize the cached data in the local memory of the synchronization server. Figure 8 , the visualization display method of synchronization data provided by the embodiment of the present application is further described. It should be noted that the synchronization server can be deployed in a cluster, that is, the synchronization server can be deployed as at least one server instance. Accordingly, at least one parameter version of all parameter versions received from the parameter management end is cached in the local memory of each server instance.

[0140] Figure 8 A schematic flow chart of a method for visually displaying synchronized data provided in another embodiment of the present application.

[0141] like Figure 8 As shown, the method for visual display of synchronization data provided in the embodiment of the present application, based on any of the above embodiments, may further include the following steps:

[0142] Step 801, in response to receiving a cache query request for a first server instance in at least one server instance triggered on a second cache query page, obtain version information of at least one parameter version cached in its local memory.

[0143] Among them, the second cache query page is a page provided by the management and control end for querying cached data in the local memory of the server instance.

[0144] The first server instance is at least one server instance among the at least one server instance deployed by the synchronization server.

[0145] Any parameter version cached in the local memory of any server instance is the parameter version sent by the parameter manager to the server instance.

[0146] In an embodiment of the present application, the second cache query page may display a button for triggering a cache query request. The cache query request is used to request a query on cached data in the local memory of any one or more server instances. The user can trigger a cache query request for the first server instance by clicking the button. Thus, in response to receiving the cache query request triggered on the second cache query page, the management and control end can call any server instance to obtain the version information of at least one parameter version cached in the local memory of the first server instance through the arbitrary server instance.

[0147] As an example, the second cache query page may include an input box or a selection box for inputting query conditions. The user may input query conditions in the input box or select query conditions in the selection box, and click the above button to trigger a cache query request for a server instance that meets the query conditions. The cache query request may carry the query conditions input or selected by the user. In response to receiving the cache query request, the management and control end may call any server instance to determine the server instance that meets the query conditions through the arbitrary server instance, and send a request to query the cache to these server instances. After these server instances obtain the version information of at least one parameter version cached in their local memory in response to the received request, they may return the version information to the arbitrary server instance, so that the arbitrary server instance may return the version information to the management and control end. Among them, the server instance that meets the query conditions is the first server instance in step 801.

[0148] The query conditions may include one or more of the host name of the server instance, the IP address, the port number of the listening port, the name and version number of the corresponding cached parameter table (where the parameter table may also be called a cache table), and the namespace.

[0149] It should be noted that the data synchronization system also includes a registration center, and each server instance deployed by the synchronization server can register information in the registration center, so that the registration center can save the attribute information of the registered server instance. When the user does not enter or select any query conditions, the at least one server instance in step 801 includes all server instances of the synchronization server that have registered information in the registration center.

[0150] Step 802: Displaying version information of at least one parameter version cached in the local memory of the first server instance on the second cache query page.

[0151] In an embodiment of the present application, version information of at least one parameter version cached in the local memory of the first server instance can be displayed in a list page on the second cache query page.

[0152] It should be noted that in the embodiment of the present application, in response to receiving a cache query request for the first server instance triggered on the second cache query page, the management end can also call any server instance to obtain the attribute information of the first server instance through the arbitrary server instance, and display the attribute information of the first server instance on the second cache query page. In addition, in the case where the parameter version includes a parameter table, the table name of at least one parameter table cached in the local memory of the first server instance can also be obtained through the arbitrary server instance, and the table name can be displayed on the second cache query page.

[0153] The attribute information of any server instance may include one or more of the host name, IP address, port number of the monitored port, server instance name, etc. of the host where the server instance is located.

[0154] For example, refer to Fig. 9 The second cache query page shown on the right may display an input box or a selection box for entering query conditions, wherein the query conditions include the host name of the host where the server instance is located, the port number of the listening port, the table name of the cache table corresponding to the cache ( Fig. 9 The user can select "ParamCerter" in the selection box corresponding to the namespace and click the "Query" button to trigger a cache query request for the server instance that meets the query condition. In response to the cache query request, the management end can call any server instance to obtain the host name, port number, instance name, and table name of the parameter table cached in the local memory (corresponding to the server instance that meets the query condition) through the server instance. Fig. 9 The cache table name in () and the corresponding version number are displayed on the second cache query page.

[0155] Among them, the steps in steps 801-802 that are similar to other embodiments can refer to other embodiments and are not described in detail here.

[0156] In this way, the version information of the parameter version cached in the local memory of the first server instance can be visually displayed, so that the user can manage the parameter version cached in the local memory of the first server instance based on the displayed version information.

[0157] As an example, at least one server instance deployed by the synchronization server can share a database, which can store all parameter versions received from the parameter management end. In order to facilitate the comparison of the version information of the parameter version in the local memory of the server instance and the database, the management end can also provide another version verification function. Accordingly, the visual display method of synchronization data provided in the embodiment of the present application can also include the following steps:

[0158] In response to receiving a version check request for a target server instance in the first server instance triggered by the second cache query page, obtaining version information of all parameter versions stored in a database of the synchronization server and version information of at least one parameter version cached in a local memory of the target server instance;

[0159] A third pop-up window is displayed on the second cache query page; wherein the third pop-up window includes version information of at least one parameter version cached in the local memory of the target server instance, and version information of all parameter versions stored in the database.

[0160] The target server instance is any one or more server instances in the first server example.

[0161] In an embodiment of the present application, when the version information of at least one parameter version in the local memory of the first server instance is displayed on the second cache query page, the selection box corresponding to each first server instance can be displayed accordingly, and the user can select the corresponding target server instance through the selection box corresponding to any one or more of the first server instances. In addition, a button for triggering a version verification request can be displayed on the second cache query page. Among them, the version verification request is used to request a comparison of the version information of the parameter version in the local memory of any one or more server instances and the database. After the user selects the target server instance and clicks the button, a version verification request for the target server instance can be triggered. Thus, the management and control end can obtain the version information of at least one parameter version cached in the local memory of the target server instance from the version information of the acquired parameter version, and call any server instance to obtain the version information of all parameter versions stored in the database through the arbitrary server instance, and display this information on the third pop-up window of the second cache query page.

[0162] As an example, in order to distinguish different server instances, the attribute information of the target server instance can also be displayed in the third pop-up window, wherein the attribute information can include one or more of the host name, IP address, port number of the monitored port, instance name, etc. of the host where the target server instance is located.

[0163] For example, the user can select Fig. 9In the example, the host name is Allenshp, and the "Version Check" button is clicked to trigger a version check request for the server instance. In response to the version check request, the management end can obtain the version information of at least one parameter version in the local memory of the target server instance, and call any server instance to obtain the version information of all parameter versions stored in the database through the server instance, and display the version information. Fig.10 The third pop-up window shown. Fig.10 The "16,17" corresponding to the "Memory Version Number" is the version information of the parameter version cached in the local memory of the server instance, and the "1,12,13,14,15,16,17" corresponding to the "Table Version Number" is the version information of the parameter version saved in the database.

[0164] Therefore, through the version verification function provided by the management and control end, the version information of the parameter version in the local memory and database of the target server instance can be displayed at the same time, so that the user can compare the version information of the parameter version in the target server instance and the database.

[0165] It is understandable that the parameter management end can send a synchronization task to the synchronization server, where the task information of the synchronization task includes the parameter version that needs to be synchronized to any business unit. After the synchronization server receives the task information of the synchronization task, it can execute the corresponding synchronization task based on the task information, that is, save the parameter version in a preset location and synchronize it to any business unit. The management and control end can also visualize the attribute information of any synchronization task to facilitate users to understand the relevant information of the synchronization task. Fig.11 , the visualization display method of synchronization data provided in the embodiment of the present application is further explained.

[0166] Fig.11 A schematic flow chart of a method for visually displaying synchronized data provided in another embodiment of the present application.

[0167] like Fig.11 As shown, the method for visual display of synchronization data provided in the embodiment of the present application, based on any of the above embodiments, may further include the following steps:

[0168] Step 1101, in response to receiving a task query request for at least one synchronization task triggered on a task query page, calls the synchronization server to obtain attribute information of at least one synchronization task through the synchronization server; wherein each synchronization task includes synchronizing a parameter version received from the parameter management end to any business unit in the distributed business system.

[0169] The task query page is a page provided by the management and control end for querying the attribute information of the synchronization task. The synchronization task may also be referred to as a data delivery task or other tasks, which is not limited in this application.

[0170] Among them, the attribute information of any synchronization task may include the version information of the parameter version in the task information of the synchronization task, the initiating system of the synchronization task, the operation type of the synchronization task (used to indicate whether it is initiated by other systems), the task description used to describe various aspects of the synchronization task, the execution status of the synchronization task (used to indicate whether the execution is successful or whether it has been merged), the creation time, the end time, the task type (such as synchronization cache), etc.

[0171] In an embodiment of the present application, the task query page may display a button for triggering a task query request. Among them, the task query request is used to request a query on the attribute information of any one or more synchronization tasks. The user can trigger a task query request for at least one synchronization task by clicking the button. Thus, in response to receiving the task query request triggered on the task query page, the management and control end can call the synchronization server to obtain the attribute information of the at least one synchronization task through the synchronization server.

[0172] As an example, the task query page may include an input box or a selection box for inputting query conditions. The user may input the query conditions in the input box or select the query conditions in the selection box, and click the above button to trigger a task query request for synchronization tasks that meet the query conditions. The task query request may carry the query conditions input or selected by the user. In response to receiving the task query request, the management end may call the synchronization server to obtain the attribute information of the synchronization task that meets the query conditions through the synchronization server, so that the synchronization server can return the attribute information of the synchronization task to the management end.

[0173] The query conditions may include one or more of the initiating system of the synchronization task, the task description, the namespace, the task type, etc.

[0174] Step 1102: Displaying attribute information of at least one synchronization task on the task query page.

[0175] In an embodiment of the present application, the attribute information of at least one synchronization task can be displayed in a list page on the task query page.

[0176] For example, refer to Fig.12The task query page shown on the right may display an input box or selection box for entering query conditions, wherein the query conditions include the initiating system, task description, namespace, and task type of the synchronization task. The user may select "ParamCerter" in the selection box corresponding to the namespace, select "All" in the selection box corresponding to the task type, and click the "Query" button to trigger a task query request for synchronization tasks that meet the query conditions. In response to the task query request, the management and control end may call the synchronization server to obtain the initiating system, operation type, task type, task description, status, creation time, end time, and version number of the parameter version in the task information of the synchronization task that meets the query conditions through the synchronization server, and display them on the task query page.

[0177] It should be noted that the reference Fig.12 For any synchronization task, when the above attribute information is displayed on the task query page, a "Details" button for viewing detailed attribute information can also be displayed. Users can click the button corresponding to any synchronization task to view the detailed attribute information of the corresponding synchronization task. For example, users can click the "Details" button corresponding to the synchronization task for synchronizing the parameter table with version number "17", so that the management end can display the following information: Fig.13 The details page of the synchronization task is shown.

[0178] In this way, the property information of at least one synchronization task can be visualized, so that the user can understand the properties and execution status of the synchronization task.

[0179] As an example, the management and control end can also visualize the attribute information of any business unit to facilitate users to understand the attribute information of any business unit.

[0180] In response to receiving an instance query request for a third business unit in the distributed business system triggered on the first instance query page, calling a synchronization server to obtain attribute information of the third business unit from a registration center through the synchronization server;

[0181] The attribute information of the third business unit is displayed on the first instance query page.

[0182] Among them, the first instance query page is a page provided by the management and control end for querying the attribute information of any business unit.

[0183] The third business unit includes any one or more business units among the multiple business units included in the distributed system.

[0184] The attribute information of any business unit may include one or more of the unit number of the business unit, the room number of the computer room, the host name of the host, the port number of the monitored port, the business unit name, the latest heartbeat time, the status, the update time of the parameter version in the local memory, etc. The business unit name is also called the instance name.

[0185] In an embodiment of the present application, the first instance query page may display a button for triggering an instance query request. The instance query request is used to request a query on the attribute information of any one or more business units. The user can trigger an instance query request for a third business unit by clicking the button. Thus, in response to receiving the instance query request triggered on the first instance query page, the management and control end can call the synchronization server to obtain the attribute information of the third business unit through the synchronization server and display it on the first instance query page.

[0186] The data synchronization system also includes a registration center. Any business unit in the distributed business system that obtains parameter versions from the synchronization server can register information in the registration center, so that the registration center can save the attribute information of the registered business unit. Therefore, the synchronization server can obtain the attribute information of the third business unit from the registration center. In addition, when the user does not enter or select any query conditions, the third business unit includes all business units in the distributed business system that have registered information in the registration center.

[0187] As an example, the first instance query page may include an input box or a selection box for entering query conditions. The user may enter the query conditions in the input box or select the query conditions in the selection box, and click the above button to trigger an instance query request for the business unit that meets the query conditions. The instance query request may carry the query conditions entered or selected by the user. In response to receiving the instance query request, the management and control end may call the synchronization server to obtain the attribute information of the business unit that meets the query conditions from the registration center through the synchronization server. Among them, the business unit that meets the query conditions is the third business unit.

[0188] The query conditions may include one or more of the unit number of the unit where the business unit is located, the room number of the computer room where the business unit is located, the host name of the host where the business unit is located, the port number of the monitored port, the business unit name, the latest heartbeat time, etc.

[0189] For example, refer to Fig.14The first instance query page shown on the right may display an input box or selection box for entering query conditions, wherein the query conditions include the unit number of the unit where the business unit is located, the computer room number of the computer room where it is located, the host name of the host where it is located, the port number of the monitored port, the instance name, and the namespace. The user can select "ParamCerter" in the selection box corresponding to the namespace, select "All" in the selection box corresponding to the port number, and click the "Query" button to trigger an instance query request for the business unit that meets the query conditions. In response to the instance query request, the management and control end may call the synchronization server to obtain the unit number, computer room number, host name, port number, instance name, latest heartbeat time, and status of the business unit that meets the query conditions through the synchronization server, and display them on the first instance query page.

[0190] Thus, the property information of the third business unit is visualized, thereby facilitating the user to understand the property information of the business unit.

[0191] As an example, the synchronization server is deployed as at least one server instance, and the management end can also visualize the attribute information of any server instance to facilitate users to understand the attribute information of any server instance.

[0192] In response to receiving an instance query request for a second server instance in the at least one server instance triggered on a second instance query page, calling any server instance in the at least one server instance to obtain attribute information of the second server instance from a registration center through the any server instance;

[0193] The property information of the second server instance is displayed on the second instance query page.

[0194] Among them, the second instance query page is a page provided by the management and control end for querying the attribute information of any server instance.

[0195] The second server instance includes any one or more server instances among the at least one server instance deployed by the synchronization server.

[0196] The attribute information of any server instance may include one or more of the unit number of the unit where the server instance is located, the computer room number of the computer room where the server instance is located, the host name of the host where the server instance is located, the port number of the monitored port, the instance name, etc.

[0197] In an embodiment of the present application, the second instance query page may display a button for triggering an instance query request. The instance query request is used to request a query on the attribute information of any one or more server instances. The user can trigger an instance query request for the second server instance by clicking the button. Thus, in response to receiving the instance query request triggered on the second instance query page, the management and control end can call any server instance to obtain the attribute information of the second server instance through the arbitrary server instance, and display it on the second instance query page.

[0198] The data synchronization system also includes a registration center. Each server instance deployed by the synchronization server can register information in the registration center, so that the registration center can save the attribute information of the registered server instance. Therefore, any server instance can obtain the attribute information of the second server instance from the registration center. In addition, when the user does not enter or select any query conditions, the second server instance includes all server instances that have registered information in the registration center.

[0199] As an example, the second instance query page may include an input box or a selection box for entering query conditions. The user may enter the query conditions in the input box or select the query conditions in the selection box, and click the above button to trigger an instance query request for the server instance that meets the query conditions. The instance query request may carry the query conditions entered or selected by the user. In response to receiving the instance query request, the management and control end may call any server instance to obtain the attribute information of the server instance that meets the query conditions from the registration center through the arbitrary server instance. Among them, the server instance that meets the query conditions is the second server instance.

[0200] The query conditions may include one or more of the unit number of the unit where the server instance is located, the computer room number of the computer room where the server instance is located, the host name of the host where the server instance is located, the port number of the monitored port, the instance name, and the like.

[0201] For example, refer to Fig.15 The second instance query page shown on the right may display an input box or selection box for entering query conditions, wherein the query conditions include the unit number of the unit where the server instance is located, the computer room number of the computer room where it is located, the host name of the host where it is located, the port number of the monitored port, and the instance name. The user can select "All" in the selection box corresponding to the port number and click the "Query" button to trigger an instance query request for the server instance that meets the query condition. In response to the instance query request, the management and control end may call any server instance to obtain the unit number, computer room number, host name, port number, and instance name of the server instance that meets the query condition through the arbitrary server instance, and display it on the second instance query page.

[0202] Thus, the property information of the second server instance is visualized, thereby facilitating the user to understand the property information of the server instance.

[0203] It should be noted that the first cache query page, the second cache query page, the task query page, the first instance query page, and the second instance query page in the embodiment of the present application may be separate pages or sub-pages of the same page.

[0204] For example, referring to the pages displayed in the above embodiments, the left side of the page may include a menu bar, including a "cache query" menu item, a first cache query page, which is a sub-page displayed on the right side of the page after the user clicks the "cache query" drop-down menu and clicks the "consumer cache query" menu item that is subsequently displayed. The second cache query page is a sub-page displayed on the right side of the page after the user clicks the "cache query" drop-down menu and clicks the "server cache query" menu item that is subsequently displayed. The task query page is a sub-page displayed on the right side of the page after the user clicks the "data distribution management" menu item. The first instance query page is a sub-page displayed on the right side of the page after the user clicks the "consumer instance" menu item. The second instance query page is a sub-page displayed on the right side of the page after the user clicks the "server instance" menu item. In addition, in the menu bar on the left side of the page, the "authority management" menu item and the "identity management" menu item can also be displayed, and the corresponding sub-pages are used to manage user permissions and user identities respectively.

[0205] With the above Figures 3 to 15 Corresponding to the method for visual display of synchronized data provided in the embodiment, the present application also provides a device for visual display of synchronized data applied to the control end. Figures 3 to 15 The embodiment provides a method for visual display of synchronized data corresponding to the embodiment, so the implementation method of the method for visual display of synchronized data is also applicable to the device for visual display of synchronized data provided in the embodiment of the present application, and will not be described in detail in the embodiment of the present application.

[0206] Fig.16 A schematic diagram of the structure of a visual display device for synchronized data provided in one embodiment of the present application.

[0207] like Fig.16 As shown, the visualization display device 1600 of the synchronization data may include an acquisition module 1601 and a display module 1602 .

[0208] The acquisition module 1601 is used to call the synchronization server in response to receiving a cache query request for at least one business unit in the distributed business system triggered on the first cache query page, so as to obtain the version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server; wherein the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit;

[0209] The display module 1602 is configured to display version information of at least one parameter version on the first cache query page.

[0210] It should be noted that the visual display device for synchronized data provided in the embodiment of the present application is applied to the control end in the above data synchronization system, and can execute Figures 3 to 15 The visual display method of the synchronization data of the illustrated embodiment. The visual display device of the synchronization data may be a control terminal, or may be configured in the control terminal.

[0211] In a possible implementation of the embodiment of the present application, at least one parameter version among all parameter versions received by the synchronization server from the parameter management end is cached in the local memory of the synchronization server;

[0212] The acquisition module 1601 is further configured to, in response to receiving a version check request for a first business unit in at least one business unit triggered on a first cache query page, acquire version information of at least one parameter version cached in a local memory of the first business unit, and call the synchronization server to acquire version information of at least one parameter version cached in its local memory through the synchronization server;

[0213] Display module 1602 is also used to display a first pop-up window on the first cache query page, which includes version information of at least one parameter version cached in the local memory of the synchronization server and version information of at least one parameter version cached in the local memory of the first business unit.

[0214] In a possible implementation of the embodiment of the present application, all parameter versions received by the synchronization server from the parameter management end are stored in a database of the synchronization server;

[0215] The acquisition module 1601 is further used to call the synchronization server in response to receiving the version check request, so as to obtain the version information of all parameter versions stored in its database through the synchronization server;

[0216] Correspondingly, the first pop-up window also includes version information of all parameter versions stored in the database of the synchronization server.

[0217] In a possible implementation of the embodiment of the present application, the acquisition module 1601 is further configured to, in response to receiving a memory occupancy query request for a second business unit in at least one business unit triggered by the first cache query page, call the synchronization server to obtain memory occupancy information of cached data in the local memory of the second business unit through the synchronization server;

[0218] The display module 1602 is further configured to display a second pop-up window on the first cache query page, wherein the second pop-up window includes memory usage information of cache data in the local memory of the second business unit.

[0219] In a possible implementation of the embodiment of the present application, the synchronization server is deployed as at least one server instance, and at least one parameter version of all parameter versions received from the parameter management end is cached in the local memory of each server instance;

[0220] The acquisition module 1601 is further configured to, in response to receiving a cache query request for a first server instance in at least one server instance triggered by the second cache query page, acquire version information of at least one parameter version cached in its local memory;

[0221] The display module 1602 is further configured to display version information of at least one parameter version cached in the local memory of the first server instance on the second cache query page.

[0222] In a possible implementation of the embodiment of the present application, the database of the synchronization server stores all parameter versions received from the parameter management terminal;

[0223] The acquisition module 1601 is further configured to, in response to receiving a version check request for a target server instance in the first server instance triggered by the second cache query page, acquire version information of all parameter versions stored in the database of the synchronization server and version information of at least one parameter version cached in the local memory of the target server instance;

[0224] Display module 1602 is also used to display a third pop-up window on the second cache query page; wherein the third pop-up window includes version information of at least one parameter version cached in the local memory of the target server instance, and version information of all parameter versions stored in the database.

[0225] In a possible implementation of the embodiment of the present application, the acquisition module 1601 is further configured to, in response to receiving an instance query request for a third business unit in the distributed business system triggered on the first instance query page, call the synchronization server to obtain attribute information of the third business unit from the registration center through the synchronization server;

[0226] The display module 1602 is further configured to display the attribute information of the third business unit on the first instance query page.

[0227] In a possible implementation of the embodiment of the present application, the synchronization server is deployed as at least one server instance; the acquisition module 1601 is further used to call any server instance in the at least one server instance in response to receiving an instance query request for a second server instance in the at least one server instance triggered on the second instance query page, so as to obtain the attribute information of the second server instance from the registration center through the any server instance;

[0228] The display module 1602 is further configured to display the property information of the second server instance on the second instance query page.

[0229] In a possible implementation of the embodiment of the present application, the acquisition module 1601 is further used to call the synchronization server in response to receiving a task query request for at least one synchronization task triggered on the task query page, so as to obtain the attribute information of at least one synchronization task through the synchronization server; wherein each synchronization task includes synchronizing a parameter version received from the parameter management end to any business unit in the distributed business system;

[0230] The display module 1602 is further configured to display attribute information of at least one synchronization task on the task query page.

[0231] The visual display device of synchronized data provided in an embodiment of the present application, in response to receiving a cache query request for at least one business unit in a distributed business system triggered on a first cache query page, calls a synchronization server to obtain version information of at least one parameter version cached in the local memory of the at least one business unit through the synchronization server, wherein the version information of at least one parameter version cached in the local memory of each business unit is received by the synchronization server from the parameter management end and synchronized to the business unit, and the version information of the at least one parameter version is displayed on the first cache query page, so as to realize the visual display of the version information of the parameter version cached in the local memory of at least one business unit, thereby facilitating the user to manage the parameter version cached in the local memory of the business unit based on the displayed version information.

[0232] According to an embodiment of the present application, the present application also provides an electronic device.

[0233] Among them, electronic equipment includes:

[0234] processor;

[0235] a memory for storing processor-executable instructions;

[0236] The processor is configured to execute instructions to implement the method for visual display of synchronized data as proposed in any of the aforementioned embodiments.

[0237] As an example, Fig.17 is a schematic diagram of the structure of an electronic device 1700 shown in an exemplary embodiment of the present application. Fig.17 As shown, the electronic device 1700 may further include:

[0238] The memory 1710 and the processor 1720, a bus 1730 connecting different components (including the memory 1710 and the processor 1720), the memory 1710 stores a computer program, and when the processor 1720 executes the program, the method for visual display of synchronized data of an embodiment of the present application is implemented.

[0239] Bus 1730 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0240] The electronic device 1700 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 1700, including volatile and non-volatile media, removable and non-removable media.

[0241] The memory 1710 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 1740 and / or cache memory 1750. The electronic device 1700 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 1760 may be used to read and write non-removable, non-volatile magnetic media ( Fig.17 not shown, usually called a "hard drive"). Although Fig.17 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical medium) may be provided. In these cases, each drive may be connected to bus 1730 via one or more data medium interfaces. Memory 1710 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of each embodiment of the present application.

[0242] A program / utility 1780 having a set (at least one) of program modules 1770 may be stored, for example, in memory 1710, such program modules 1770 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 1770 generally perform the functions and / or methods of the embodiments described herein.

[0243] The electronic device 1700 may also communicate with one or more external devices 1790 (e.g., keyboard, pointing device, display 1791, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1700, and / or communicate with any device that enables the electronic device 1700 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 1792. In addition, the electronic device 1700 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) through a network adapter 1793. As shown, the network adapter 1793 communicates with other modules of the electronic device 1700 through a bus 1730. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0244] The processor 1720 executes various functional applications and data processing by running the programs stored in the memory 1710 .

[0245] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the method for visual display of synchronized data in the embodiment of the present application, and will not be repeated here.

[0246] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and the above instructions can be executed by a processor of an electronic device to complete the visual display method of synchronized data proposed in any of the above embodiments. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0247] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, characterized in that when the computer program / instruction is executed by a processor, the method for visual display of synchronized data proposed in any of the above embodiments is implemented.

[0248] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the inventions claimed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary techniques in the art that are not claimed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0249] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for visual display of synchronous data, characterized in that: The method comprises: In response to receiving a cache query request for at least one business unit in the distributed business system triggered on a first cache query page, calling a synchronization server to obtain, through the synchronization server, version information of at least one parameter version cached in a local memory of the at least one business unit; wherein the version information of at least one parameter version cached in the local memory of each of the business units is received by the synchronization server from a parameter management end and synchronized to the business unit; The version information of the at least one parameter version is displayed on the first cache query page.

2. The method according to claim 1, characterized in that: The synchronization server caches at least one parameter version of all parameter versions received from the parameter management terminal in a local memory of the synchronization server; the method further comprises: In response to receiving a version check request for a first business unit among the at least one business unit triggered on the first cache query page, obtaining version information of at least one parameter version cached in a local memory of the first business unit, and calling the synchronization server to obtain version information of at least one parameter version cached in its local memory through the synchronization server; A first pop-up window is displayed on the first cache query page, wherein the first pop-up window includes version information of at least one parameter version cached in the local memory of the synchronization server and version information of at least one parameter version cached in the local memory of the first business unit.

3. The method according to claim 2, characterized in that The synchronization server receives all parameter versions from the parameter management terminal, and stores them in a database of the synchronization server. The method further includes: In response to receiving the version check request, calling the synchronization server to obtain version information of all parameter versions stored in its database through the synchronization server; Correspondingly, the first pop-up window also includes version information of all parameter versions.

4. The method according to claim 1, characterized in that The method further comprises: In response to receiving a memory occupancy query request for a second business unit in the at least one business unit triggered on the first cache query page, calling the synchronization server to obtain memory occupancy information of cached data in a local memory of the second business unit through the synchronization server; A second pop-up window is displayed on the first cache query page, and the second pop-up window includes memory usage information of the cache data.

5. The method according to claim 1, characterized in that The synchronization server is deployed as at least one server instance, and the local memory of each server instance caches at least one parameter version of all parameter versions received from the parameter management end; the method further includes: In response to receiving a cache query request for a first server instance in the at least one server instance triggered by the second cache query page, obtaining version information of at least one parameter version cached in its local memory; The second cache query page displays version information of at least one parameter version cached in the local memory of the first server instance.

6. The method according to claim 5, characterized in that The database of the synchronization server stores all parameter versions received from the parameter management terminal; the method further includes: In response to receiving a version check request for a target server instance in the first server instance triggered on the second cache query page, obtaining version information of all parameter versions stored in a database of the synchronization server and version information of at least one parameter version cached in a local memory of the target server instance; A third pop-up window is displayed on the second cache query page; wherein the third pop-up window includes version information of at least one parameter version cached in the local memory of the target server instance, and version information of all parameter versions stored in the database.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: In response to receiving an instance query request for a third business unit in the distributed business system triggered on the first instance query page, calling the synchronization server to obtain attribute information of the third business unit from a registration center through the synchronization server; The attribute information of the third business unit is displayed on the first instance query page.

8. The method according to any one of claims 1 to 6, characterized in that The synchronization server is deployed as at least one server instance; the method further comprises: In response to receiving an instance query request for a second server instance in the at least one server instance triggered on a second instance query page, calling any server instance in the at least one server instance to obtain attribute information of the second server instance from a registration center through the any server instance; The attribute information of the second server instance is displayed on the second instance query page.

9. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: In response to receiving a task query request for at least one synchronization task triggered on a task query page, calling the synchronization server to obtain attribute information of the at least one synchronization task through the synchronization server; wherein each of the synchronization tasks includes synchronizing a parameter version received from the parameter management end to any business unit in the distributed business system; The attribute information of the at least one synchronization task is displayed on the task query page.

10. A visual display device for synchronized data, characterized in that: It is characterized in that The device comprises: An acquisition module is used for, in response to receiving a cache query request for at least one business unit in the distributed business system triggered on a first cache query page, calling a synchronization server to obtain version information of at least one parameter version cached in a local memory of the at least one business unit through the synchronization server; wherein the version information of at least one parameter version cached in the local memory of each of the business units is received by the synchronization server from a parameter management end and synchronized to the business unit; A display module is used to display version information of the at least one parameter version on the first cache query page.

Images